Mgetty 1.1.14

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

Hi,

no idea what could be causing this -- 1.1.14 has definitely no problems
with glibc, so the timeout mechanism really should work.  Dunno why it
doesn't, maybe you'll want to contact someone at RedHat support about it.

In this case below, it looks very much like a dialout program that didn't
get its locking done correctly, thus messing up mgetty's line.  Make sure
the dialout program creates the UUCP style lock file listed below.

gert


Scott Dudley wrote:
> 
> Gert,
> 
> I just noticed another hung mgetty port but a different scenario.  Here's the log:
> 
> 04/13 08:32:41 1a5  waiting...
> 04/13 09:30:18 1a5    select returned 1
> 04/13 09:30:18 1a5   checking lockfiles, locking the line
> 04/13 09:30:18 1a5   makelock(ttyQ1a5) called
> 04/13 09:30:18 1a5   do_makelock: lock='/var/lock/LCK..ttyQ1a5'
> 04/13 09:30:18 1a5   lock made
> 04/13 09:30:18 1a5  waiting for ``RING''
> 04/13 09:30:18 1a5   got: at&f2s0=1s7=255[0d]
> 04/13 09:30:18 1a5    CND: OKat&f2s0=1s7=255[0d][0d][0a]OK[0d]
> 04/13 09:30:18 1a5    CND: OK[0a]
> 
> Hope this provides some enlightening detail.  Any advice appreciated.
> 
> Thanks.
> 
> 
> --------------------------------------
> Scott Dudley, Telesoft Corp.
> 
> Phone: (602) 308-1115
>    FAX: (602) 308-1300
>  Email: scott@telesoft.com
> 
> 


-- 
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