mgetty-1.1.9 on Solaris2.5.1/Sparc

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Martin Spott wrote:
> This is what you requested:
> 
> > There was *NO* lock file from minicom here, or it was not valid. Please
> > try again, with "mgetty -x9", and just show me this part, between
> >  "waiting..."
> > and
> >  "waiting for ``RING''"
> 
> 
> 12/16 23:51:52 a/b waiting...
> 
> [ starting minicom ]
> 
> 12/16 23:54:47 a/b select returned 1
> 12/16 23:54:47 a/b checking lockfiles, locking the line
> 12/16 23:54:47 a/b makelock(cua/b) called
> 12/16 23:54:47 a/b get_lock_name(cua/b) called
> 12/16 23:54:47 a/b -> ttyname /dev/cua/b
> 12/16 23:54:47 a/b lock file: /var/lock/LK.032.029.131073
> 12/16 23:54:47 a/b do_makelock: lock='/var/lock/LK.032.029.131073'
> 12/16 23:54:47 a/b lock made

Hmmm. I'd say "there is no lock file from Minicom with *that* name
here". If mgetty finds a file with that name, it will write some message
to the log file, like "stale lock file from pid 1234" or something
similar.

Maybe Minicom creates "classic" lock files (LCK..cuab) instead of SVR4
ones?

gert
-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-35655025    gert.doering@physik.tu-muenchen.de
.