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

Previous Next

Full log

Message #29 received at 2520 <at> debbugs.gnu.org (full text, mbox):

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

Stefan Kangas [2021-10-22 02:19:21] wrote:
> 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...

Not really: they're turned into input events and one of them can be used
for `debug-on-event` but the other is free.

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

BTW, if someone wants to re-read their init file upon SIGUSR1, they can
do so via something like:

    (define-key special-event-map [sigusr1] <...>)


-- Stefan

Previous Next

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