Im trying to use the crate in a simple project just to start a daemon to do some =thing simple. I have added daemonize-me = "1.0" to my Cargo.toml. When I run cargo build I get the following:

Compiling daemonize-me v1.0.0
error[E0432]: unresolved imports `libc::prctl`, `libc::PR_SET_NAME`
--> /Users/conordowney/.cargo/registry/src/github.com-1ecc6299db9ec823/daemonize-me-1.0.0/src/ffi.rs:6:12
 |
6 | use libc::{prctl, PR_SET_NAME};
 |            ^^^^^  ^^^^^^^^^^^ no `PR_SET_NAME` in the root
 |            |
 |            no `prctl` in the root

For more information about this error, try `rustc --explain E0432`.
error: could not compile `daemonize-me` due to previous error

My program is just a hello world. I just wanted to see if it would build with the package included. Any idea what might be wrong?

Currently I use the privileged_action in daemonize to open some files in /proc/self before the process changes user/group so I can sample some stats about the running process. I have not found another approach that may work for this - if I open the files before demonize.start they will be referring not to the process I want to be monitored.

Is there possibility to add optional privileged_action method that takes a FnOnce? For reference: https://docs.rs/daemonize/latest/daemonize/struct.Daemonize.html#method.privileged_action

Hi there!

I've been using this library to create a daemon for a program I use. It works perfectly, but I don't know how to interact with it later.

Is there any function (or could there any that could be implemented) to check if the daemon is already running, and if so communicate with it? Even just getting its PID would already be useful, even better if it's possible to communicate natively with it.

Thanks in advance for your help :)

Is your feature request related to a problem? Please describe.

This doesn't seem to work with tokio. When I try, I get this message:

thread 'main' panicked at 'failed to wake I/O driver: Os { code: 9, kind: Uncategorized, message: "Bad file descriptor" }'

Additional context

This specifically happens when I run Daemon::start from a main with #[tokio::main].

**Is your feature request related to a problem?

Hey @DarthUdp, amazing work, I've been using daemonize-me for sometime now, and I'd like to have the ability to to start/restart, get status and stop. So that I can create a daemon object and have a set of methods.

Describe the solution you'd like

• Start method to accept a function that block the daemon from being killed and be killed if sigterm was received.
• Stop/kill method to kill daemon and execute a user provide cleanup function.
• Restart method to kill the daemon and run start method.
• Status method to pretty print stdout and stdin.

Additionally, it would be awesome if user can provide app name as in clap and description.

Describe alternatives you've considered

I've implemented a semi-independent wrapper for my use case. Here's a gist.

https://gist.github.com/tami5/af81b31307d7cb9e51f31b55e16180ea

This is a maintenance release to the 1.0-LTS series, it fixes issues preventing the code from building on BSD and MacOS and a segfault that arose when that was fixed.

To Reproduce Steps to reproduce the behavior: In async_std-based app having async_std::task::sleep().await hangs forever when started under daemonize-me.

Expected behavior Shouldn't hang

Desktop:

• OS: Ubuntu
• Version 20.10

Additional context I've tried daemonize crate first and got the same issue. I guess it is somehow related to this crate's internals?

Describe the bug Passing an invlid uname or gname causes panic.

To Reproduce Steps to reproduce the behavior: On the construction of the struct give it an invalid uname/gname, it will cause a panic

Expected behavior A recoverable error should happen not a panic

Desktop (please complete the following information): Any platform regardless of tier