Re[2]: LCK and reboot
I have had this issue when using the application 'dip' to control dialup
SLIP/PPP connections. It puts lock files in the same directory and would not
allow itself access to the modem port if the .LCK file was present. As you
probably figured, the .LCK file does not get deleted unless the application(s)
that work with it terminate cleanly and clean up after themselves.
Since at boot time no locks should be "on", you could enter a command at boot
time that discriminately (or indiscriminately) removes all .LCK files from the
directory.
John Roesch
Robot Research, Inc,
johnr@robot-research.com
______________________________ Reply Separator _________________________________
Subject: Re: LCK and reboot
Author: debian-user@Pixar.com at robot_gate
Date: 3/26/96 1:58 PM
In your email to me, David H. Silber, you wrote:
>
> > I've noticed that if I reboot a machine while someone is dialed into it,
> > the LCK file in /var/spool/uucp never gets cleaned up, rendering that
> > line unusable till the LCK file is removed. Is this repeatable by
> > anyone else?
>
> Shouldn't that be /var/lock/LCK? (Is this /my/ uucp package?)
Umm... I dunno... mgetty puts LCK files there by default, along with pppd
and ( I think) minicom..
> Yes, I'm sure that has happened to me. Could you submit a bug report so
> that I don't lose track of this?
You bet!
Tim
--
sailer@sun10.sep.bnl.gov
"Have you ever seen an atom, Little bits of everything floating by,
Take a good look at them, Collectively they compose all you see
including your eye" - "Whoops" - Blues Traveler
** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
Reply to: