*BSD News Article 62288


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!yarrina.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in1.uu.net!usc!howland.reston.ans.net!surfnet.nl!sun4nl!xs4all!kick.knooppunt.be!not-for-mail
From: lblancke@kick.knooppunt.be (Lieven Blancke)
Newsgroups: comp.unix.bsd.bsdi.misc,comp.unix.bsd.freebsd.misc
Subject: Re: Controlling Ports
Followup-To: comp.unix.bsd.bsdi.misc,comp.unix.bsd.freebsd.misc
Date: 26 Feb 1996 19:40:03 -0000
Organization: KnoopPunt
Lines: 51
Message-ID: <4gt2aj$l2p@kick.knooppunt.be>
References: <4g9ms7$puj@news.atnet.net> <4ghavq$o36@uriah.heep.sax.de>
NNTP-Posting-Host: kick.knooppunt.be
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:2489 comp.unix.bsd.freebsd.misc:14447

We had the same problem on our FreeBSD 2.0.5 system!  A 'ps -ax' gave this:

  704 d3- RN   878:31.38 pine
16915 d3- RN   1868:43.26 pine

As you can see those two pine processes (that were running on ttyd3) have
a '-' sign.  This means they are not connected to the terminal anymore.  

To solve this problem, we made a small program that scans for any 'bash' or 
'pine' process that isn't attached to any terminal anymore, and kills it.

Any other ideas?

Lieven Blancke


J Wunsch (j@uriah.heep.sax.de) wrote:
: jwshafto@atnet.net (John Shafto) writes:

: (Disclaimer: i'm not a user of BSD/OS.  But i've seen your question
: hanging around for some time.  Just guesses.)

: > 1.) When user hangs up in Pine or Lynx (amoung others) BSDI does not
: > shut down jobs associated with the port, and worse, the modem doesn't
: > reset, nor does the getty restart on the port.  Hence, there is then
: > a line in the middle of the hunt group that won't answer (until the
: > errant job is killed, then everything resets).

: Some programs like Lynx (or even the old vi and the old ftp, under
: Illtrix) are known to cause problems with a dead tty line.  They
: apparently ignore an error condition when reading, thus spinning
: forever in the input loop.  This is most likely (without looking in
: the code) the fault of these programs.

: I don't have an idea however why the o/s doesn't free the process
: group on loss of carrier, so that a new getty will be spawned to the
: modem.  Unless, of course, the applications (intentionally or accid-
: entally) turned the modem tty line into a ``local'' one, thus making
: the driver ignore modem control signals.  The application should not
: be allowed to do this, but that's kinda misconception in Unix.

: -- 
: cheers, J"org

: joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
: Never trust an operating system you don't have sources for. ;-)

-- 
mailto:lblancke@knooppunt.be
http://www.knooppunt.be/~lblancke/