On Thu, 10 Apr 1997, Dr. Rich Artym wrote:
> 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.
Given that all Exim seems to need is a prod in this case (which is being
investigated to see if I can fix something), it might be that just a
plain kill or kill -INT is good enough.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
