[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [SUGGESTION] nohup_${PID}.out
From: |
Bernhard Voelker |
Subject: |
Re: [SUGGESTION] nohup_${PID}.out |
Date: |
Mon, 19 Feb 2018 09:09:06 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
On 02/19/2018 12:30 AM, Boruch Baum wrote:
I hope the list will continue to consider
the entirety of the suggestions in my post.
What exactly do you refer to? I think the other suggestions
seem to be based on knowing the PID, so given that this doesn't change
due to execve(), a workaround seems to be possible already, e.g.
a custom output logfile name "nohup.PID.out":
exec nohup some/prg > nohup.$$.out
Regarding an option writing the PID: well, what about all the other
utilities executing other processes like env, nice, time, ionice,
xargs, ...?
It sounds like to become quite some bloat to the code of all the utilities
of this class - especially as the PID does not change due to execve().
Have a nice day,
Berny