nix
nix copied to clipboard
nix-rust
Rust friendly bindings to *nix APIs
The latest nix crate fails to build on illumos based systems (and almost certainly Solaris systems) since both the `TCP_KEEPCNT` and `TCP_KEEPINTVL` TCP options aren't defined in the libc crate....
This mirrors the behaviour of `Ipv4Addr::any()` but for IPV6 addresses. Unless I missed something, `libc` doesn't export anything resembling `INADDR_ANY` for IPV6, so the zeroes are hardcoded. I can't imagine...
Is there some reason that we have both [`nix::time::ClockId`](https://docs.rs/nix/0.19.0/nix/time/struct.ClockId.html) and [`nix::sys::timerfd::ClockId`](https://docs.rs/nix/0.19.0/nix/sys/timerfd/enum.ClockId.html)? It seems like `nix::time::ClockId` is more complete - defining more types of clocks for different operating systems. It looks...
This is my proposed change for #323 This is a breaking change, existing code will have to add an additional `None` argument to the constructor to get the previous behaviour.
The ability to set an interface index value should be exposed in https://github.com/nix-rust/nix/blob/5e3c954596f12512ba8728c437345a529ec48b0a/src/sys/socket/multicast.rs#L34 Related to https://github.com/carllerche/mio/issues/377
The value type is a `libc::c_uint` since that's what's returned by `nix::net::if_::if_nametoindex`. I haven't gated the sockopt for any particular target_os since it seems to be widely supported by the...
The link to the Linux kernel list of ioctl numbers appears to have moved, at least as of the time this issue was created (_latest_ kernel is `5.8.14`). Existing (broken)...
`gettimeofday`, ~`clock_gettime`~, ~`clock_settime`~, ~`clock_getres`~, `nanosleep` and `clock_nanosleep` seem to be supported by various *nixes (at least Linux and FreeBSD), but bindings are not included in this crate. I'd be happy...
Tested nix@566e2d7dad025c9b2bef98115b584328c145675d using rust 1.47.0 (stable) on Ubuntu 20.04/AMD64 (up to date at time of testing) `cargo test` hangs on `test_af_alg_aead` (to be file after this one). Once commented out,...
