Name
SIGUSR1
Synopsis
Beginning with V8.6.5, sendmail responds to a SIGUSR1 signal. This signal causes sendmail to syslog at LOG_DEBUG the several items that define its state.[1] That syslog output begins with a line that looks like this:
--- dumping state onreason
: $j =val
---
where reason
can be any one of the
following:
user signal
The information has been logged because sendmail received a SIGUSR1 signal. In this instance the daemon logs the information and continues to run.
daemon lost $j
The information has been logged because a running daemon discovered that the value in
$j
(the canonical name of this host, $j) disappeared from the class$=w
(the list of all names by which the local host is known, $=w). This test is made and this information is logged only if sendmail was compiled with XDEBUG defined (XDEBUG). In this instance the daemon logs the information and aborts.daemon $j lost dot
The information has been logged because a running daemon discovered that the value in
$j
(the canonical name of this host, $j) was no longer canonical (no longer contained a dot inside it). This test is made and this information is logged only if sendmail was compiled with XDEBUG defined (XDEBUG). In this instance the daemon logs the information and aborts.
Whichever the reason, the information that is logged for each looks pretty much the same; for example:
--- dumping state onreason
: $j =val
--- CurChildren =num
NextMacroId =nextid
(Maxmaxid
) --- open file descriptors: --- ← output of ...
Get Sendmail, 3rd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.