On Mon, 27 Mar 2000, Marilyn Davis wrote:
> But exiwhat doesn't say anything very useful for me:
>
> [root@deliberate /tmp]# exiwhat
> 528 3.02 daemon: -q15m, listening on port 25
That suggests the other Exim processes are so stuck they aren't even
responding to exiwhat. I suggest you kill all the exim processes except
528 that are older than a few hours.
> [root@deliberate /tmp]# ps -ef | grep exim
> root 528 1 0 Mar09 ? 00:00:00 /usr/local/bin/exim -bd -q15m
> root 3380 1 0 Mar14 ? 00:00:00 [exim]
> majordom 3385 3380 0 Mar14 ? 00:00:00 [exim]
> majordom 3387 3385 0 Mar14 ? 00:00:00 [exim]
> root 19005 1 0 Mar16 ? 00:00:00 [exim]
> majordom 19006 19005 0 Mar16 ? 00:00:00 [exim]
> majordom 19008 19006 0 Mar16 ? 00:00:00 [exim]
> root 9333 649 1 10:00 tty1 00:00:03 emacs exim_mainlog
> root 9404 9336 0 10:06 ttyp0 00:00:00 grep exim
>
> Am I doing something wrong that I have these old [exim] processes and
> that some are owned by majordom?
Exim processes that are running as majordom should be delivery
processes, delivering stuff *to* Majordomo, I think. That does look
suggestive:
> root 3380 1 0 Mar14 ? 00:00:00 [exim]
> majordom 3385 3380 0 Mar14 ? 00:00:00 [exim]
> majordom 3387 3385 0 Mar14 ? 00:00:00 [exim]
3380 could be a queue runner; its child 3385 could be a delivery process
and its child 3387 the local delivery pipe process. Ditto for the other
triplet. But why they should all be stuck beats me!
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
