NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/unix/ultrix/9014

Internet Message Format | 1992-12-21 | 1.6 KB

Path: sparky!uunet!cs.utexas.edu!uwm.edu!linac!att!cbnews!cbnewsm!cbnewsl!att-out!pacbell.com!iggy.GW.Vitalink.COM!lll-winken!olympic.llnl.gov!kchiles
From: [e-mail] (Keith Chiles)
Newsgroups: comp.unix.ultrix
Subject: 4.3 and shared modems
Message-ID: <[e-mail]>
Date: 21 Dec 92 16:43:55 GMT
Sender: [e-mail]
Reply-To: [e-mail] (Keith Chiles)
Organization: Digital Equipment Corporation
Lines: 26
Nntp-Posting-Host: olympic.llnl.gov

HOHOHO Netland,

For those who might be affected by this, I have found an
interesting feature in Ultrix 4.3 that kindly resets the
kernel when you exit a tip session.  In fact it works with
several packages as they hang up a shared modem line.
The way it seems to work is that if you have a 5000/125
or a 5000/25, and you are using tip with a modem configured
as being shared, when the modem hangs up the line it
lets the kernel shut down (Just ignore those old panic
messages, the're not important anyway) and allows you
to boot a new kernel from the >> prompt.  This is much
better than 4.2's old method of just hanging up the line
and going on with things.

The workaround is to avoid shared modem use.  I was just
wondering if anyone else was encountering this problem
and if you are, you might not want to spend a whole lot
of time trying to figure out what you are doing wrong.
If you are considering going up to 4.3, you might want
to move carefully and with real neat 4.2 backups if you
are working with a communications front-end. I also hear
this feature works for uucp.

Cheers, Keith
[e-mail]