GNU bug report logs - #2520
Read configuration file on SIGUSR1

Previous Next

Full log

View this message in rfc822 format

From: Stefan Kangas <stefan <at> marxist.se>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: rfrancoise <at> debian.org, Andreas Schwab <schwab <at> linux-m68k.org>, Stefan Monnier <monnier <at> iro.umontreal.ca>, cmr.Pent <at> gmail.com, 2520 <at> debbugs.gnu.org
Subject: bug#2520: 23.0.91; Dies on SIGHUP
Date: Fri, 22 Oct 2021 02:19:21 -0700

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Andreas Schwab <schwab <at> linux-m68k.org> writes:
>
>> On Sep 29 2019, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
>>
>>> It's definitely something I could have used a number of times...  and
>>> re-reading init files on SIGHUP isn't an unusual thing to do.
>>
>> But only for demons.  Normally a process receives SIGHUP if its
>> controlling terminal goes away.
>
> Yeah, that's true.
>
> I guess SIGUSR1 and 2 are also taken...

So do we actually want to do anything here?  Simply re-reading the
configuration comes with its own set of complications for us.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.