Section: Maintenance Commands (8)Updated: March 26, 2003Local indexUp
exiwhat - Finding out what Exim processes are doing
On operating systems that can restart a system call after receiving a
signal (most modern OS), an
process responds to the SIGUSR1 signal by writing a line describing what
it is doing to the file exim-process.info in the Exim spool directory.
script sends the signal to all
processes it can find, having first emptied the file.
It then waits for one second to allow the
processes to react before displaying the results.
In order to run
successfully you have to have sufficient privilege to send the signal to
processes, so it is normally run as root.
uses to find
processes varies in different operating systems.
Not only are different options used, but the format of the output is
For this reason, there are some system configuration options that configure
If it doesn't seem to be working for you, check the following compile-time
the command for running "ps"
the argument for "ps"
the argument for "egrep" to select from "ps" output
the argument for the "kill" command
An example of typical output from
164 daemon: -q1h, listening on port 25
10483 running queue: waiting for 0tAycK-0002ij-00 (10492)
10492 delivering 0tAycK-0002ij-00 to mail.ref.example [10.19.42.42]
10592 handling incoming call from [192.168.243.242]
10628 accepting a local non-SMTP message
The first number in the output line is the process number.
The third line has been split here, in order to fit it on the page.
This manual page needs a major re-work. If somebody knows better groff
than us and has more experience in writing manual pages, any patches
would be greatly appreciated.