Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.unix.shell
Subject: Re: nohup Versus setsid
Date: Thu, 12 Sep 2024 23:13:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <vbvsie$fkeu$3@dont-email.me>
References: <vbtqcd$2sce$1@dont-email.me> <vbujqm$1t0jr$1@news.xmission.com>
	<vbul72$89jc$1@dont-email.me> <vbvod2$esm6$1@dont-email.me>
	<vbvs6r$7jlu$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 13 Sep 2024 01:13:19 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="fe8eaca0c36637cab02c0b5baab677cf";
	logging-data="512478"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+4CGIGKVK7a4Ih6WZ/bCHN"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:KhFmjA31OvYAy0xV02///jaiZiU=
Bytes: 1655

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.