🚀 go-pugleaf

Probably the idle is because it's been idle that long since receiving
anything from the other end or transmitting anything. The conn-term I
would guess is because they are not talking for some odd reason.

Adam Bisbe wrote:
> 
> A 08:20 07/05/98 -0400, Stuart Pierce escribi�:
> >Here's a list of syn11, I did notice that the EOF flag was not there.
> >
> >
> >Line     Modem/Dvc  CharGrp    Use          Command    DeviceStatus
> >syn11    <<None>>   <<None>>   newlex       <<None>>
> ><CTS,DCD,DSR,RTS,DTR>
> >Flags:  001d604f
> ><DEBUG,CTS,DCD,DSR,NOLOGIN,NOAUTO,SYNC,NOAUTOID,DEDICATED,RTS,DTR>
> >DSR: ON        DCD: ON        CTS: ON       RTS: ON       DTR: ON
> >Speed: 56000    Flow control: none   Parity: none   Size: 8   Stop: 1
> >Login: OFF         PPP PAP: auto       PPP CHAP: auto
> >Autoconfigure: off     Callin: ON         Access: all
> >Modem command delay: 0.000 seconds    Login prompt delay: 0.250 seconds
> >Modem status delay (seconds): DCD=0.000     DSR=0.000     CTS=0.000
> >DTR off time: 3.000 seconds
> >Idle times (minutes): receive=125  transmit=6  (auto-reset=0 dtron)
> Idle should be 0. Why do you have idle time on that line?
> 
> >Trace: ON        Callback monitor: OFF
> >IP address: 207.40.12.99
> >Terminal type: <<None>>        Rows: not set        Cols: not set
> >Process = syn11, Dial Protocol = Console, state = Conn-Term
> state should be idle, not Conn-Term.
> 
> Adam.