Sujet : Re: nohup Versus setsid
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.unix.shellDate : 13. Sep 2024, 00:13:19
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vbvsie$fkeu$3@dont-email.me>
References : 1 2 3 4 5
User-Agent : Pan/0.160 (Toresk; )
On Thu, 12 Sep 2024 23:07:07 -0000 (UTC), vallor wrote:
On Thu, 12 Sep 2024 22:02:10 -0000 (UTC), Lawrence D'Oliveiro wrote:
The effect is supposed to be the same: spawn a background task that
will continue running after you log out.
That's not the only thing that the (POSIX) nohup(1) tool does.
Then I can watch for status without flooding the terminal:
But then, you cannot do more than one nohup invocation at a time, if one
is already writing to nohup.out.
With setsid, I just specify an output log file for each invocation, and I
can tail that in the usual way, same as you do.
nohup Versus setsid
Re: nohup Versus setsid