public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Grindal Bakken <hgb@ifi.uio.no>
To: util-linux@vger.kernel.org
Subject: login/telnet problems
Date: 30 Jan 2013 12:41:52 +0100	[thread overview]
Message-ID: <x2efw1iyk1r.fsf@diamant.ifi.uio.no> (raw)


Hi.  I'm working on a product which (sadly) requires telnet, and after
an upgrade from util-linux-2.20 to 2.22.2, telnet starts acting up by
dropping the first character (at least that's the easiest problem to
spot).

I looked around, and determined that the problem was related to
upgrading login(1).  Further, I bisected util-linux, and determined
that the problem was introduced by:

commit 2e7035646eb85851171cc2e989bfa858a4f00cd4
Author: Karel Zak <kzak@redhat.com>
Date:   Thu Jul 12 16:33:52 2012 +0200

    login: close tty before vhangup()
    
    Let's close all tty file descriptors before vhangup() call.
    
    References: https://lkml.org/lkml/2012/6/5/145
    Signed-off-by: Karel Zak <kzak@redhat.com>


I reverted that commit locally, and telnet started working nicely
again.  This is netkit-telnet-0.17, btw.

It's not a huge problem for me to keep a local revert of this commit,
but I thought perhaps you wanted to know it did actually break
something (although one can argue the very existence of telnet these
days is a bug...).


-- 
Henrik Grindal Bakken <hgb@ifi.uio.no>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52


             reply	other threads:[~2013-01-30 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 11:41 Henrik Grindal Bakken [this message]
2013-02-01 16:31 ` login/telnet problems Karel Zak
2013-02-01 17:29   ` Henrik Grindal Bakken

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=x2efw1iyk1r.fsf@diamant.ifi.uio.no \
    --to=hgb@ifi.uio.no \
    --cc=util-linux@vger.kernel.org \
    /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