From: Russell King <email@example.com>
To: "Martin J. Bligh" <firstname.lastname@example.org>,
Cc: linux-kernel <email@example.com>
Subject: Re: [Bug 982] New: cu -l /dev/ttyS0 got a signal hangup in 2.5 kernel
Date: Tue, 5 Aug 2003 12:58:54 +0100 [thread overview]
Message-ID: <20030805125854.B30676@flint.arm.linux.org.uk> (raw)
In-Reply-To: <firstname.lastname@example.org>; from email@example.com on Sun, Jul 27, 2003 at 10:13:54PM -0700
On Sun, Jul 27, 2003 at 10:13:54PM -0700, Martin J. Bligh wrote:
> Distribution: SuSE SLES8
> Hardware Environment:NetVista 6579-A4U Pentium III - 866 MHz 256MB RAM
> Software Environment:2.5.75 kernel
> Problem Description: cu session fails to log into the other machine which is connected with a
> null modem serial cable between serial ports.
> It works fine in 2.4.19 4GB kernel
> Steps to reproduce:
> 1. connecting two systems with a null modem serial cable between serial ports.
> 2. On one machine, do : cu -l /dev/ttyS0
> On other system, have /sbin/agetty -L 9600 ttyS0 vt100 running.
> and ttyS0 has been defined in /etc/securetty
> 3. cu session connected and showed you the login prompt.
> 4. Got a hangup signal and disconnected after typing "root" or any user ID.
> It supposes to prompt you "password:" to let you type the password of the other machine
> to login to that system.
If I remember to update bugzilla...
What seems to be happening is that cu is clearing the "clocal" termios bit.
This means that when the CD line is dropped on ttyS0, cu receives a hangup
signal, as per the POSIX spec. This seems reasonable.
There is a change of behaviour between 2.4 and 2.5 kernels though
(please confirm) - if you use the "callout" devices in 2.4, you don't
receive this hangup signal, even if the clocal bit is cleared. Callout
devices no longer exist in 2.5.
The real question is this - why is the CD line being dropped between the
two machines between typing in the user name and asking for the password.
Maybe someone with this problem can give some details about the system
they're trying to log into rather than the local system.
Russell King (firstname.lastname@example.org) The developer of ARM Linux
prev parent reply other threads:[~2003-08-05 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 5:13 [Bug 982] New: cu -l /dev/ttyS0 got a signal hangup in 2.5 kernel Martin J. Bligh
2003-08-05 11:58 ` Russell King [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).