Trailblazer and comatose mode [was Re: No reset??]

[Lyndon Nerenberg]

In article <494 at icus.islp.ny.us> lenny at icus.islp.ny.us (Lenny Tropiano) writes:
>What I've noticed is that it happens with calls terminate abnormally, 
>either hung up or possibly some sort of long BREAK signal.  It might
>also have to do with the XON/XOFF handshaking, the modem getting
>a XOFF, and never getting the paired XON.  For some reason the modem
>doesn't reset.  It will not accept commands, or for that matter incoming
>calls.
>
>My kludge is to kill the uugetty (which drops DTR, therefore resetting
>the modem) every 1/2 hour.  I hope the BA4.01 ROMs fix this problem.
>I hope the upgrade is free as well... since there are bugs in the ROMS.

There will always be bugs in the firmware... This business of free
upgrades has been beaten to death before! Our cure to the lockup problem
is also to kill the getty on a regular basis. This is best handled
by making sure DCD is actually tracking the true carrier state, and
adding "-t 120" to the {uu}getty parameter list. In this mode, the
getty will recycle 120 seconds after DCD is asserted unless someone
has logged in. This will drop DTR which (should) force a modem
reset.

[ The -t flag may not be documented in your man page, however it
  exists in every V7 and later getty/uugetty I've seen. BSD uses
  the "to" entry in gettytab. I'm not sure how 4.3 does it. ]

-- 
VE6BBM   {alberta,pyramid,uunet}!ncc!lyndon  lyndon at Nexus.CA