mgetty locking problem.

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

Hi,

MARK A BROWN wrote:
>      I am using Linux (RedHat Linux 5.0 Intel - kernel 2.0.32) to manage a 
>      modem pool consisting of 8 hayes 33.6 modems hung off a Cyclades 
>      CYCLOM-8yo 8 port serial board (using devices ttyC0 - ttyC7).
>      
>      I am using mgetty-1.1.9-3 (binary RPM distributed with RedHat 5) to 
>      handle dial-in on 3 of the 8 modems, the remaining 5 modems are 
>      dedicated to dial-out using pppd-2.3.3.

Don't use 1.1.9 with RH 5.0.  It doesn't work reliably due to problems
with GNU libc 2.

>      During certain portions of the day I need to use all 8 modems for 
>      dial-out, mgetty is supposed to work with pppd as long are both are 
>      using the same locking scheme and devices (and I believe they are).

Sure, no problem here.

>      The problem is, mgetty seems to be leaving the modems it is watching 
>      (ttyC0,ttyC1 and ttyC2) locked.   Once it initializes the modems (data 
>      only) it leaves the lock file (LCK..ttyC0, etc.) containing the PID 
>      for the mgetty watching it in the /var/lock directory preventing pppd 
>      from using the device.   

It does not (during normal operations) - but this might be caused by the
well-known 1.1.9/rh5.0 problems.

>      Does anyone have any ideas on what may be going on and how I might 
>      resolve it?

In any case, if you ask on the mailing list,  please include a mgetty
log file showing the problem.

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