The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] 4.3BSD help: getty ignoring modem status
Date: Sun, 19 Mar 2017 02:37:12 -0400 (EDT)	[thread overview]
Message-ID: <20170319063712.3E54C18C09F@mercury.lcs.mit.edu> (raw)

    > From: Warren Toomey

    > 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?

I know very little of 4.x, but I did write a V6 DZ driver, back in the
Cenozoic or some such time period... :-)

Looking at the 4.3Tahoe (which particular 4.3 version is in question here,
anyway?) DZ driver:

  http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Tahoe/usr/src/sys/vaxuba/dz.c

I find it hard (without further digging) to figure out how it gets from where
it should discover carrier has gone away (in dzrint(), from dztimer()) to the
rest of the system; they have added some linesw[] thing I don't know about.

Looking at the 4.2 driver:

  http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/vaxuba/dz.c

it seems (in the same routine) to do the right thing:

               gsignal(tp->t_pgrp, SIGHUP);

so in that version, it's sending a SIGHUP to the whole pgroup when the
carrier goes away - which should be the right thing.

	Noel


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  6:37 Noel Chiappa [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2017-03-19  5:57 Warren Toomey
2017-03-19  6:18 ` Larry McVoy
2017-03-19  8:06 ` Warren Toomey
2017-03-19  9:57   ` Jacob Goense
2017-03-19 10:08   ` Warren Toomey

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=20170319063712.3E54C18C09F@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).