Re: Queue weirdness

[Matt Simpson <net-qmlist@xxxxxxxxx>]

At 10:01 AM 2/6/08, John Palkovic wrote:
> I sometimes do 'find /var/qmail/queue -type f -print'. I would guess 
> there must be some message files in /var/qmail/queue/mess/*. 
> Corresponding files in the other dirs will have the same filename 
> (which is the inode number). It's documented in the INTERNALS file 
> in the qmail source.

Thanks.  I see:

crossbo# find /var/qmail/queue -type f -print
/var/qmail/queue/bounce/236086
/var/qmail/queue/mess/2/238282
/var/qmail/queue/mess/9/237323
/var/qmail/queue/mess/14/236086
/var/qmail/queue/mess/17/247589
/var/qmail/queue/mess/19/237402
/var/qmail/queue/mess/19/247591
/var/qmail/queue/mess/20/247592
/var/qmail/queue/mess/21/236139
/var/qmail/queue/mess/21/237105
/var/qmail/queue/mess/21/247593
/var/qmail/queue/info/14/236086
/var/qmail/queue/remote/14/236086
/var/qmail/queue/lock/tcpto
/var/qmail/queue/lock/sendmutex


I assume 14/236086 is a legitimate message which is being handled 
normally, and the other mess files are remnants of the crash.  They 
all appear to be empty.  If I'm comprehending the INTERNALS document 
correctly, this corresponds to state S2, and will be cleaned up after 
36 hours.  Does that sound correct?

At 4:18 PM 2/6/08, ed wrote:
> Try running John Simpson's qfix script on your queue, it's available
> form his site here:
>
>   http://qmail.jms1.net/scripts/qfixq.shtml

Thanks for that, also.  It arrived it as I was writing the above.  At 
this point, I think I'll wait to see if qmail's own cleanup handles 
the problem.  If the files don't go away in 36 hours, I'll probably 
try John's qfix.