Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!oddjob!gargoyle!ddsw1!igloo!learn
From: learn@igloo.UUCP (william vajk)
Newsgroups: comp.unix.xenix
Subject: Re: Microport: ttyM1, Modem Problem - (nf)
Message-ID: <409@igloo.UUCP>
Date: 23 Feb 88 23:59:33 GMT
References: <23000001@nixpbe.UUCP>
Organization: igloo, Northbrook, IL
Lines: 31
Summary: sometimes it works....

In article <23000001@nixpbe.UUCP>, kebsch@nixpbe writes:

> I did put this line in /etc/inittab: t1:2:respawn:/etc/getty ttyM1 1200 ,
> called telinit q and got a getty on ttyM1 running.

our line reads    '18:2:respawn getty ttyM1'

we handle the speed with /etc/gettydefs, which required a minor
rehack to contain 300, 1200, and 2400 baud. The modem comes on line
as soon as the system hits multiuser (init level 2) after boot up.

> It is possible to login via the modem, but after hang up (Phone/Modem)
> the shell respectively the last invoked program is still running.
> I expected a hangup signal that kills the running program, so that getty
> is restarted. The "Carrier Dedect" signal changed in the right way.
> Has anybody experience with this problem and knows how to fix it?

we sometimes have a user that hangs up improperly and does not 'exit'
the system. this tends to either leave processes running, or in the
worse case, confuse the system to a point that DTR will not come back
up. Once this has happened, any manipulation (eg having root kill the
getty for the tty) results in a system crash (double panic) and requires
a reboot to make the system usable again.

We also invoke the following line in .profile in ~home

stty intr '^c' kill '^u' erase '^h' echoe

a ^d or 'exit' logs the user off properly, terminates the processes,
and resets the DTR on the modem, respawns getty.

Bill Vajk                                          learn@igloo