Xref: utzoo comp.unix.questions:28762 comp.unix.sysv386:5041
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!world!dcc
From: dcc@world.std.com (Dave C Curado)
Newsgroups: comp.unix.questions,comp.unix.sysv386
Subject: modem mileage
Message-ID: <1991Feb17.122852.26711@world.std.com>
Date: 17 Feb 91 12:28:52 GMT
Distribution: na
Organization: The World
Lines: 27


I've got a question concerning a modem.  I think there's probably a simple
solution to my problem, but since I don't know it yet...

We have a 386 running ICS 3.2 as an internet node.  Unfortunately for me,
it's located 70 miles away from our main site, and we must always call
in to the machine via good ol' 2400 baud modems.  This works fine, until
you have the occasion to drop the session in an ungraceful sort of way...
as in, hanging up the phone.  (for various reasons)
When this happens, it seems as if the modem freeks out and sits there
trying to communicate with the shell process I've left running.  This ties
up the machine so badly, that you can't login.  Even standing at the console!
280 miles later, (two round trips to go and fix the problem)
my tires and I are looking for a 'better way.'
 Some ideas we've had:
    - alter the kernel resources to only give so many resources to a process
    - try to make a daemon that would watch for this sort of tie up, and would
       kill the process.
    - be very very careful when dialing in (not so easy during thunder storms)
 
                                  Dave C.

-- 
Dave Curado                I didn't say that I didn't say it.      
dcc@world.std.com          I said that I didn't say that I said it.
Omnet Inc.                 I want to make that very clear                     
                                 --former Mich. gov. George Romney