Bug#332198: [Pkg-shadow-devel] Bug#332198: login: unable to determine TTY name, got /dev/pts/1

[Alexander Gattin]

tags 332198 moreinfo
thanks

What are versions of dash, rsh-client and rsh-server
used?

On Wed, Oct 05, 2005 at 06:13:58PM +0200, Christian Perrier wrote:
> Quoting Marc Lehmann (debian-reportbug at plan9.de):
> > Version: 1:4.0.3-35
> > 
> > 
> > Directly after a fresh reboot eeboot, "rsh rebooted-host" results in an
> > immediate connection close, and the syslog on the remote host says:
> > 
> >    Oct  5 06:12:36 cerebro in.rlogind: Connection from root at fuji for root
> >    Oct  5 06:12:36 cerebro pam_rhosts_auth[452]: allowed to root at fuji as root
> >    Oct  5 06:12:36 cerebro login[453]: (pam_unix) session opened for user root by root(uid=0)
> >  > Oct  5 06:12:36 cerebro login[453]: unable to determine TTY name, got /dev/pts/1 
> >    Oct  5 06:12:36 cerebro in.rlogind[452]: Closing connection with root at fuji
> > 
> > "/dev/pts/1" looks like a perfectly fine tty name to me. Subsequent rsh
> > calls work fine.
> > 
> > I think at least the error message should be clearer, right now it is
> > wrong, as it did correctly determine the tty name, and something else
> 
> Can you try reproducing this with login and passwd packages from sid ?

I tried with new login, rlogin-ed OK on pts/0 and pts/1...
// sh -> bash on my system BTW

> I actually think that the "unable to determine TTY name" from login is
> maybe not *the* cause of the problem.

But after RTFS, I think this error msg is really
misleading...

-- 
WBR,
xrgtn