Re: 'screen' error: "Must be connected to a terminal"

2001-11-03 Thread Karsten M. Self
on Sat, Nov 03, 2001 at 08:05:48AM -0600, Adam Lazur ([EMAIL PROTECTED]) wrote: > Alan Shutko ([EMAIL PROTECTED]) said: > > ii libc6 2.2.4-5GNU C Library: Shared libraries and > > Timezone > > > > Works fine. > > Yes, the bug that Karsten is describing is a bug in libc6 2.2.4-4,

Re: 'screen' error: "Must be connected to a terminal"

2001-11-03 Thread Karsten M. Self
on Sat, Nov 03, 2001 at 08:05:48AM -0600, Adam Lazur ([EMAIL PROTECTED]) wrote: > Alan Shutko ([EMAIL PROTECTED]) said: > > ii libc6 2.2.4-5GNU C Library: Shared libraries and > > Timezone > > > > Works fine. > > Yes, the bug that Karsten is describing is a bug in libc6 2.2.4-4,

Re: 'screen' error: "Must be connected to a terminal"

2001-11-03 Thread Adam Lazur
Alan Shutko ([EMAIL PROTECTED]) said: > ii libc6 2.2.4-5GNU C Library: Shared libraries and Timezone > > Works fine. Yes, the bug that Karsten is describing is a bug in libc6 2.2.4-4, specifically in ttyname() not working properly for setgid executables. Running a version of lib

Re: 'screen' error: "Must be connected to a terminal"

2001-11-02 Thread Alan Shutko
Wayne Topa <[EMAIL PROTECTED]> writes: > Currently running screen, root & user, with no such errors. > #dpkg -l screen libc6 > screen 3.9.10-0.1 > libc6 2.2.4-3 >^ you have -4 ii libc6 2.2.4-5GNU C Library: Shared libraries and Timezone Works fine. --

Re: 'screen' error: "Must be connected to a terminal"

2001-11-02 Thread Wayne Topa
Karsten M. Self(kmself@ix.netcom.com) is reported to have said: > on Fri, Nov 02, 2001 at 12:50:04PM -0800, Karsten M. Self > (kmself@ix.netcom.com) wrote: > > See subject. > > > > When I invoke screen as an unpriviledged (ordinary) user, I get the > > following error: > > > > [EMAIL PROTECT

Re: 'screen' error: "Must be connected to a terminal"

2001-11-02 Thread Karsten M. Self
on Fri, Nov 02, 2001 at 12:50:04PM -0800, Karsten M. Self (kmself@ix.netcom.com) wrote: > See subject. > > When I invoke screen as an unpriviledged (ordinary) user, I get the > following error: > > [EMAIL PROTECTED]:karsten]$ screen > Must be connected to a terminal. > > I *can* invoke

Re: 'screen' error: "Must be connected to a terminal"

2001-11-02 Thread Karsten M. Self
on Fri, Nov 02, 2001 at 04:06:10PM -0500, Justin R. Miller ([EMAIL PROTECTED]) wrote: > Thus spake Karsten M. Self (kmself@ix.netcom.com): > > > Anyone else seeing this, or have a fix? > > I believe this was reported as a libc bug. Last night's updates for me > seemed to have fixed it. Hmm...I

Re: 'screen' error: "Must be connected to a terminal"

2001-11-02 Thread Justin R. Miller
Thus spake Karsten M. Self (kmself@ix.netcom.com): > Anyone else seeing this, or have a fix? I believe this was reported as a libc bug. Last night's updates for me seemed to have fixed it. -- Justin R. Miller <[EMAIL PROTECTED]> PGP/GnuPG Key ID 0xC9C40C31 (preferred) pgpPsh6v5Qcwe.pgp Descr

'screen' error: "Must be connected to a terminal"

2001-11-02 Thread Karsten M. Self
See subject. When I invoke screen as an unpriviledged (ordinary) user, I get the following error: [EMAIL PROTECTED]:karsten]$ screen Must be connected to a terminal. I *can* invoke screen as a root user. I note that the binary is installed SGID utmp: [EMAIL PROTECTED]:karsten]$ ll