nc
nc copied to clipboard
Run *nix system calls directly in Rust
Version: 0.8.20 Steps to reproduce: ``` $ uname -ar Linux shrimp-paste 6.8.9-300.fc40.ppc64le #1 SMP Thu May 2 18:35:21 UTC 2024 ppc64le GNU/Linux (Fedora 40) $ rustc --version rustc 1.77.0 (aedd173a2...
Hi, having issues building nc with --target=i686-unknown-linux-gnu, tried building youki and ran in to this error, cloned nc itself and built, and reproduced the same build error, default target builds...
I've modified a little the [original example](https://docs.rs/nc/latest/nc/fn.rt_sigaction.html#example) in order to make sure. The `handle_sigterm` function doesn't seem to be called ever. I've also tried other signals like SIGWINCH and other...
The example shown on the README didn't pass any args: ``` let pid = unsafe { nc::fork() }; match pid { Ok(pid) => { if pid == 0 { println!("child...
In `struct linux_dirent`: - offset of d_name is: 18 - offset of d_reclen is: 16 While in `nc::linux_dirent_t`: - offset of d_name is: 24 - offset of d_reclen is: 16...
Currently, the library uses the `unreachable!` macro to mark code paths that should never be reached. However, this macro generates additional panic-related code, which is unnecessary for our use case...
Thanks for the awesome crate and great work! I am the main author of [syd](https://lib.rs/crates/syd) and we've been using nc in our project with great joy. Below is an error...