nohup: programs that are waiting for stdin exit with 0 instead of 1
Open
Nobody has claimed this yet.
U - nohup
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
GNU:
$ nohup date --file -; printf $?
nohup: ignoring input and appending output to 'nohup.out'
1
uutils:
$ cargo run -p uu_nohup date --file -; printf $?
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.07s
Running `target/debug/nohup date --file -`
nohup: ignoring input and appending output to 'nohup.out'
0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the uu_nohup package and reproduce the issue using date --file - through the command shown. Trace how nohup handles stdin and propagates the child status; done means the command exits with status 1, matching GNU nohup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100