On Wed, Nov 11, 2020 at 02:34:57PM -0600, Derek Martin wrote:
On Sat, Nov 07, 2020 at 01:06:00PM +0100, Matthias Apitz wrote:
Does whatever the server is doing affect the mutt process too,
despite mutt setting its own handler and blocking SIGCHLD during the
fork/exec?
No, it does not. Mutt will start with the default signal
dispositions. Signal handler changes are copied across fork(), but
NOT across exec().
not _entirely_:
During an execve(2), the dispositions of handled signals are reset to
the default; the dispositions of ignored signals are left unchanged.
(from the notes in linux' sigaction(2) man page.)
i don't think that changes the conclusion in this case, though.
