The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] 4.3BSD help: getty ignoring modem status
Date: Sat, 18 Mar 2017 23:18:54 -0700	[thread overview]
Message-ID: <20170319061854.GA28286@mcvoy.com> (raw)
In-Reply-To: <20170319055736.GA26709@minnie.tuhs.org>

This sounds like a setsid() like problem.  As in the server is not 
cleaning up.  BSD didn't have setsid, I think that was a POSIX thing
and it was one of the good things that POSIX added.  That's my 
memory, someone will correct it.

On Sun, Mar 19, 2017 at 03:57:36PM +1000, Warren Toomey wrote:
> Hi all, over on the uucp project we are struggling with a problem. If a
> user is logged in with telnet, and they disconnect the telnet session,
> their shell hangs around. The next person that telnets in gets the shell.
> 
> SimH, with the -a -m flags on a simulated DZ line, has these modem flags:
> 
> Telnet connected:    Modem Bits: DTR RTS DCD CTS DSR
> Telnet disconnected: Modem Bits: DTR RTS         DSR
> 
> So, DCD and CTS are being dropped, but getty (or something) isn't responding
> and (presumably) sending a HUP signal to the shell.
> 
> Is there anybody with some modem or getty knowledge that can help?
> 
> Thanks, Warren



-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 


  reply	other threads:[~2017-03-19  6:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  5:57 Warren Toomey
2017-03-19  6:18 ` Larry McVoy [this message]
2017-03-19  8:06 ` Warren Toomey
2017-03-19  9:57   ` Jacob Goense
2017-03-19 10:08   ` Warren Toomey
2017-03-19  6:37 Noel Chiappa
2017-03-19  7:46 ` Warren Toomey
2017-03-19 13:44 ` Paul Ruizendaal
2017-03-20  0:47   ` Erik E. Fair
2017-03-20  1:25     ` Erik E. Fair
2017-03-20  2:25       ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170319061854.GA28286@mcvoy.com \
    --to=lm@mcvoy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).