> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of David > F. Skoll > Sent: Wednesday, January 18, 2006 2:03 PM > To: [email protected] > Subject: Re: [Mimedefang] BIG problems with mimedefang > > > Gary Funck wrote: > > > Lisa Casey wrote: > > >> 11859 defang 10 0 30572 20M 1852 D 6.3 4.0 0:10 mimedefang.pl > >> 11657 defang 10 0 30172 9252 1820 D 3.0 1.8 0:07 mimedefang.pl > >> 11652 defang 9 0 29184 8400 1832 D 2.9 1.6 0:07 mimedefang.pl > > > Try running strace on one of those busy slaves to see what > > sort of system calls it is making. > > They're all in "D" state -- waiting for disk I/O. > > I bet /var/spool/MIMEDefang is not on a ramdisk. >
Might be a good guess, but why did this suddenly start becoming a problem? Maybe 'strace' (combined with info. from 'lsof') would offers some insight into which files are being accessed? Any other ways to debug running Perl processes? Can the mimedefang "master" somehow start the slaves so they can later be debugged, or is there a related technique? _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
