Hello,
I asked a while ago as to how I could determine when a queue runner process
was processing the waiting mail. It was suggested that I use 'exiwhat'. This
works fine generally, but if I issue a 'runq &' command beforehand then I
get error messages from exiwhat:
{Exim-P}311: exiwhat
sh: kill: permission denied
sh: kill: permission denied
5892 3.16 handling incoming connection from sender35.lodo.exactis.com
[192.147.174.186]
6563 3.16 handling incoming connection from (mequake.lys) [194.154.122.2]
The two kill's seem to be trying to signal 'USR1' to the runq command itself.
'ps -ef' shows that runq appears twice - I assume this is correct in its
processing of the queue.
If I do the same as root then I get no errors, but do get the entry:
7413 3.16 running queue: waiting for children of 7431
which is what I want. However, I do not want to run exiwhat from root.
It seems that whilst exiwhat works fine generally, sending a signal to exim
when it is run from a soft link (runq) won't work unless you are root
(probably because you are signalling a root process? (exim being suid root)).
Anyone any thoughts about this - I still want to be able to tell if a queue
runner is running, but not by having to use root.
Thanks,
John.
--------------------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: jhorne@???
PGP key available from public key servers
