In message <3.0.1.32.19970407122313.006d7f1c@???>,
John C. Ring, Jr. writes:
> Occasionally, I'm seeing messages sit on the queue for very long periods of
> time. Looking through the logs, on each time the queue would run, the log
> for such messages would be "Spool file is locked". I next found with "ps"
> that the (I assume) original process for each such message still existed,
> clearly showing why the file was still locked :)
Just a small hint in case you're intending to script up something to
deal with the problem, or rather, with its symptoms: get the message
identifiers with "mailq", then use "fuser" on the corresponding -D files
in spool/input, and pass the returned pids to kill -TERM to release the
locks. A nice one-liner.
Rich.
--
########### Dr. Rich Artym ================ PGP public key available
# galacta # Email : rich@??? 158.152.156.137
# ->demon # Web : http://www.galacta.demon.co.uk - temp page only
# ->ampr # AMPR : rich@g7exm[.uk].ampr.org 44.131.164.1 BBS:GB7MSW
# ->NTS # Fun : Unix, X, TCP/IP, kernel, O-O, C++, SoftEng, Nano
########### More fun: Regional IP Coordinator Hertfordshire + N.London
