mgetty 1.1.9 and Supra FaxModem 28.8

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

> Scott Dudley wrote:
> > I'm running mgetty 1.1.9 on a Red Hat 5.0 system with Supra FaxModem 
28.8's
>
> Don't.  Upgrade to 1.1.10 or higher if you use RH 5.0, because 1.1.9
> doesn't work correctly with GNU libc.
>
> > flashed to 33.6.  It's only been running for a week but occasionally,
> > mgetty holds the uucp lock on the port and won't release.
>
> This happens if something timeouts, or better, *would* timeout,  because
> timeout handling of 1.1.9 with GNU libc is broken.
>
> (Klaus - can we add this to the FAQ?)
>
> gert
>

OK Gert, I upgraded to 1.1.14 but I'm still experiencing the same problem. 
 Following is the output of one of my logs.  mgetty just "sits" here until 
I kill it.  It then respawns and everything is fine.  What's going on here?

04/12 05:53:03 1a4  check for lockfiles
04/12 05:53:03 1a4   checklock: stat failed, no file
04/12 05:53:03 1a4  locking the line
04/12 05:53:03 1a4   makelock(ttyQ1a4) called
04/12 05:53:03 1a4   do_makelock: lock='/var/lock/LCK..ttyQ1a4'
04/12 05:53:03 1a4   lock made
04/12 05:53:04 1a4   tio_get_rs232_lines: status: RTS CTS DSR DTR
04/12 05:53:04 1a4  lowering DTR to reset Modem
04/12 05:53:04 1a4   tss: set speed to 38400 (017)
04/12 05:53:04 1a4   tio_set_flow_control( HARD )
04/12 05:53:04 1a4   waiting for line to clear (VTIME), read:
04/12 05:53:04 1a4  send: \dATQ0V1H0[0d]
04/12 05:53:05 1a4  waiting for ``OK''
04/12 05:53:05 1a4   got: A[d4]Q0V1H0[0d]
04/12 05:53:05 1a4    CND: A_Q0V1H0

Another one shows:

04/12 02:05:25 1a5  send: \dATQ0V1H0[0d]
04/12 02:05:26 1a5  waiting for ``OK''
04/12 02:05:26 1a5   got: ATQ0V1H0[0d]
04/12 02:05:26 1a5    CND: ATQ0V1H0

I manually tested the string ATQ0V1H0 and the modems don't complain.  Your 
assistance is greatly appreciated.