help it won't start after a crash

Pablo Idiaquez (mfkr@inf.utfsm.cl)
Wed, 29 Nov 1995 23:29:20 +0100


Hi 
    I need a Little help with mgetty , so I think that here is a nice
    place to found it .
    
    I am using Linux as ISP server, I first start using  uugetty and 
    it work nice but have a little problem , users spent a lot of time
    ringing until it get the first RING , and then send the ATA.
    Well I decide to moving to mgetty, and it work fine it listen really
    to the _first_! RING and establish the connection .
          My problem with mgetty is that when loose carrier , and 
    the executed program remain still live i.e. a bash or a sliplogin, mgetty
    won't start again .
          I suspect that my problem is with the run level on inittab
    for uugetty i used
    s3:123456:respawn:/sbin/uugetty ttyS3 F38400 vt100
    and I try with mgetty with a lot of ways having the same result
    s3:123456:respawn:/usr/local/sbin/mgetty -x 9 -s 38400 ttyS3
    For this line I'm using a GVC 14.400 bps.
    
    Other question: I have another line with an old external packard bell
    2400 bps modem, that has not hardware support for v42bis, but it
    can be supplied by softwre , there is a serial driver that can
    supply this protocol for my modem ( under linux ), because 
    during connection phase whith most 14.400 modems, those send to
    my little modem a lot of caracters that I suppose are owned by
    the protocol negotioation, and those character are taken by mgetty
    as input for login and make mgetty hungup a while after CONNECT 2400
    message any hint will be welcome ....
    
    thank's in advance
    
    Pablo
    
---    
Pablo Idiaquez R. 2nd year Informatik std. at UTFSM , Chile
Keywords: modems, Slip, ISP, Security, Linux.
Reply-To: mfkr@inf.utfsm.cl  
          mfkr@mezcal.valparaiso.cl