|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
On Tue, 25 May 1999, Jason Lenthe wrote:
> This has happened to me before. What I have found that works is just do an su
> then startup minicom as root then exit. This way its able to re-lock the file
> and unlock it. I can't explain why /var/lock was clean, though.
>
> Jason
Thank you. I'll try that next time.
>
> At 07:50 AM 5/25/99 -0400, you wrote:
>
> >
> > I was using Minicom 1.82.1 with a debugger yesterday when the power went
> > out. I was logged in as user. After the power
> >
> > came back on I couldn't get back in to Minicom (when logged in as user), it
> > said that /dev/cua0 was locked.
> >
> > I checked /var/lock (the configured lockfile path) and it was clean. I could
> > use Minicom if I was logged in as root.
> >
> > I didn't have time to futz around, so I did a make install of Minicom and it
> > then came back for user. Anyone know what
> > happened ?
> >
> > *******************************************
> > Tom Borawski
> > PO Box 8418
> > Philadelphia, PA 19101-8418
> >
> > TomBorawski@IEEE.org
> > *******************************************
>
>
>
> --
> To unsubscribe, send a message with the word 'unsubscribe' in the subject
> or body of your message to plug-request@lists.nothinbut.net
>
>
****************************************
Tom Borawski
PO Box 8418
Philadelphia, PA 19101-8418
TomBorawski@IEEE.org
--
To unsubscribe, send a message with the word 'unsubscribe' in the subject
or body of your message to plug-request@lists.nothinbut.net
|
|