public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: bernd@rhm.de
To: linux-kernel@vger.kernel.org
Subject: Login on 2.6.x: can't reopen tty
Date: Wed, 16 Feb 2005 23:14:30 +0100 (MEZ)	[thread overview]
Message-ID: <200502162214.XAA29751@node130.rhm.de> (raw)

Hi all, hope I'm not of topic here but had no response elsewhere...
                                     
we observe a problem with login starting with kernel 2.6. Actually
the problem still exists in 2.6.11-rc3-bk3-20050206171922-bigsmp
which we loaded from SuSE. We never saw this problem before and
we used nearly every release in the past. The problem:
                                                               
When we try to login to a remote machine with telnet or rsh we
sometimes fall back immediately with the message 'connection closed'.
When we try again the login mostly succeeds. The ratio of bad/good
attempts over all is 1/10. It doesn't depend on the state of the 
machines e.g. type if hardware or load. It happens on laptops as
well as smp-machines. In messages we see:
                                                           
 "login[xxx]: FATAL: can't reopen tty: No such file or directory"
                                                                 
We debugged login and tracked the problem down to the fopen of
/dev/pts/nn in function opentty() just after a call to the kernel
function vhangup().
                              
The questions:
 
   - why does /dev/pts/nn disappear (and never comes back)?
   - is this a kernel bug? is there something wrong in vhangup()?
   - is anybody else aware of this problem?
     (there's only one additional posting from Yehavi Bourvine)
   - is there a solution (pending)?
                                       
Thanks in advance for any hint, we are pretty losts...
                              
Greetings
Bernd Rieke

                 reply	other threads:[~2005-02-16 22:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200502162214.XAA29751@node130.rhm.de \
    --to=bernd@rhm.de \
    --cc=linux-kernel@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