[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[SUGGESTION] nohup_${PID}.out
From: |
Boruch Baum |
Subject: |
[SUGGESTION] nohup_${PID}.out |
Date: |
Sun, 18 Feb 2018 06:26:59 -0500 |
User-agent: |
NeoMutt/20171215 |
ref: nohup (GNU coreutils) 8.23
1] Wouldn't it be useful for nohup to indicate the PID of the process it
spawns?
1.1] What comes to mind would be to have nohup send the PID to
either STDOUT or STDERR, and also to send it as a first line to its
output file.
1.1.1] It would also be helpful for nohup to send to its output file
the text of the command line that it spawned.
1.2] This would be useful to help:
1.2.1] track the process
1.2.2] send it signals
1.2.3] identify what exactly this output file is recording
1.3] This behavior would be consistent with what bash does when ending
a comamnd with '&'; it indicates the PID and job number.
2.] Also, I would find it useful for nohup to have options to produce a
{quasi-,}unique output file:
2.1] nohup_${PID}.out
2.2] nohup_${PID}_${RANDOM}.out
For your consideration,
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
- [SUGGESTION] nohup_${PID}.out,
Boruch Baum <=