Re: Nohup and wget

[Tim Rühsen]

Hi Lionel,

this seems to be an nohup / ssh issue.

It looks like wget (or better: your script) receives another signal than 
SIGHUP. It might be SIGPIPE, which is typical when you try to write to a 
stream that has been closed or has no reader any more. This may be the 
reason why it works with -q: the closed stream isn't detected and no 
SIGPIPE is generated.

Hm, just seeing that SIGPIPE is ignored by wget... so looks like my 
guess was wrong. Without further working into, I can't exactly say.

Regards, Tim

On 31.05.21 22:54, Lionel_deschamps wrote:
> Hi all !
>
> It might be a bug in wget (or me not being a pro with messages ...).
>
> I wrote a simple bash program performing some periodic wget request and 
some sleeps between each request called prequest.sh
> I do execute this program through ssh and I would like this program to run even 
> if ssh connexion is lost.
> I did use in ssh : nohup ./prerequest >/dev/null 2>&1 &
>
> Now here is my “bug”
>
> If I use wget with -q option, it runs fine and keeps running even if 
> disconnected
> I I use directly wget without -q, it runs fine but wget are not performed if 
> i’m disconnected. Prequest seems to run as the sleeps are done.
>
> I honnestly see no links between the -q option (no output) and the ssh 
> disconnection effects and I’m very interested in understanding the issue or let 
> you know that there might be a bug in wget.
>
> Thansks all and have a great day.
>
> Lionel Deschamps

OpenPGP_signature
Description: OpenPGP digital signature