------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1007
Nigel Metheringham <nigel@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Exim 4.73 |Exim 4.77
Phil Pennock <pdp@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #7 from Phil Pennock <pdp@???> 2012-01-18 09:08:56 ---
This was all fixed by Tony in TF/03 of Exim 4.77.
=======================8< cut here >8=========================
TF/03 Make the exiwhat support code safe for signals. Previously Exim might
lock up or crash if it happened to be inside a call to libc when it
got a SIGUSR1 from exiwhat.
The SIGUSR1 handler appends the current process status to the process
log which is later printed by exiwhat. It used to use the general
purpose logging code to do this, but several functions it calls are
not safe for signals.
The new output code in the SIGUSR1 handler is specific to the process
log, and simple enough that it's easy to inspect for signal safety.
Removing some special cases also simplifies the general logging code.
Removing the spurious timestamps from the process log simplifies
exiwhat.
=======================8< cut here >8=========================
If anyone still sees this problem from 4.77 onwards, please re-open this bug
with details.
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
