Xref: utzoo comp.mail.uucp:1488 news.sysadmin:848
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!ncar!oddjob!gargoyle!att!jhc
From: jhc@att.ATT.COM (Jonathan Hawbrook-Clark)
Newsgroups: comp.mail.uucp,news.sysadmin
Subject: Re: HDB uustat
Message-ID: <2212@att.ATT.COM>
Date: 19 Jul 88 21:54:35 GMT
References: <126@carpet.WLK.COM>
Reply-To: jhc@att.ATT.COM (Jonathan Hawbrook-Clark)
Followup-To: comp.mail.uucp
Distribution: na
Organization: AT&T ISL Middletown NJ USA
Lines: 17

In article <126@carpet.WLK.COM> bill@carpet.WLK.COM (Bill Kennedy) writes:
>After polling rutgers and killing the process I still get
>rutgers		Locked
>in my uustat -m display.  Where is it coming from?

Betcha you've got a file /usr/spool/locks/LCK..rutgers.
It might be in /usr/spool/uucp/LCK..rutgers, but you say
that you've checked there. It's the machine's lockfile.
If you poll rutgers again with debug on then you'll see it
testing the lockfile for validity (there's a PID inside it)
and then deleting it and creating a new one.

comp.mail.uucp was 'the right choice'... (sorry, couldn't resist).
-- 
Jonathan Clark		jonathan@mtune.att.com, attmail!jonathan
Any affiliation is given for identification purposes only.

The Englishman never enjoys himself except for some noble purpose.