SIGUSR1

Tell sendmail to dump its states sendmail signal

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.[220] That syslog output begins with a line that looks like this:

--- dumping state on reason: $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 on page 830) disappeared from the class $=w (the list of all names by which the local host is known, $=w on page 876). This test is made and this information is logged only if sendmail was compiled with XDEBUG defined (XDEBUG on page 152). 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 on page 830) 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 on page 152). 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 on reason: $j = val --- ...

Get sendmail, 4th Edition now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.