Rust library to ease the task of creating daemons, I have drawn heavy inspiration from Daemonize by knsd.
1.0-LTS track: 1.0.2
Add it to your cargo.toml this will add the whole 1.0.x (LTS) series as compatible as per semver
daemonize-me = "1.0"
Example:
```rust
extern crate daemonizeme;
use daemonizeme::{Daemon, Group, User};
use std::convert::TryFrom;
use std::fs::File;
fn main() { let stdout = File::create("info.log").unwrap(); let stderr = File::create("err.log").unwrap(); let daemon = Daemon::new() .pidfile("example.pid", Some(false)) .user(User::tryfrom("daemon").unwrap()) .group(Group::tryfrom("daemon").unwrap()) .umask(0o000) .workdir(".") .stdout(stdout) .stderr(stderr) .start();
match daemon {
Ok(_) => println!("Daemonized with success"),
Err(e) => eprintln!("Error, {}", e),
}
} ```
I will try to keep support for linux, freebsd and macos
| os | tier | | --- | --- | | linux | tier 1 | | freebsd, netbsd | tier 2 | | macos, unix, *nix | tier 3 | | Anything non unix | not supported |
For tier 1 any code that breaks the tests and or ci/cd is blocking for a release, tier 2 compilation errors are release blocking, tier 3 are supported on a best effort basis, and build failure as well as test failures are not blocking.
note on custom/hobby OS support, if your os implements the syscalls used in lib.rs with behavior that is equivalent then this library is likely to work but it's even less of a guarantee.
LTS versions are marked as such in the current release, those have a lifetime of 6 months after the release of the next version.
Non LTS versions will only be supported until the next version:
i.e: 1.0.x is an LTS version, when 2.0.0 lands it will be supported for 6 more months. within releases patches are NOT LTS.
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.