🚀 go-pugleaf

> I fire off a "uucico -r1" from cron every half-hour to clean out the
> spool area.  There are only two ports and we talk to 3 machines.
> Neither of the ports are hung.  Things are back to normal.  The
> spooling area is reasonably clean.  The logfile shows many "LOCKED
> (system name)" messages all within several minutes of each other for
> each of the systems we talk to.  There was some traffic going on at
> that point.  Any ideas?
>
There's one way this can easily happen.  If machine X has received
two or more mail messages to be forwarded to machine Y, uucico will
start up a uuxqt daemon to process them, and each one will run rmail
to forward the mail.  Each rmail will start up a new uucico to try 
to push its mail message through.  It is highly likely that they
will all run at the same time, and all but the first will generate
the LOCKED (Y) message.  

This happens here all the time.  I just ignore it.

-- 

	John M Chambers 
Phone: 617/364-2000x7304
Email: ...{adelie,bu-cs,harvax,inmet,mcsbos,mit-eddie,mot[bos],rclex}!cdx39!{jc,news,root,usenet,uucp}
Smail: Codex Corporation; Mailstop C1-30; 20 Cabot Blvd; Mansfield MA 02048-1193
Telex: 922-443 CODEX A MNSF
Clever-Saying: For job offers please call at home (617/484-6393) evenings and weekends.