On Wed, 13 Sep 2000, David S. Miller wrote:
> Date: Wed, 13 Sep 2000 09:25:28 -0400 (EDT)
> From: "Richard B. Johnson" <root@chaos.analogic.com>
>
> I haven't a clue why a UID/GID=0 process can't acquire a
> controlling TTY.
>
> It probably is some bogosity to do with process groups
> of the init kernel thread which execve's init.
>
> Later,
> David S. Miller
> davem@redhat.com
> -
I'm checking on it now. Here's a strace with setsid() ahead, same
problem:
close(3) = 0
mprotect(0x4000c000, 569344, PROT_READ|PROT_WRITE) = 0
mprotect(0x4000c000, 569344, PROT_READ|PROT_EXEC) = 0
SYS_136(0, 0x1, 0x4009c02c, 0xbffff77c, 0xbffff774) = 0
getpid() = 6
setsid() = 6
open("/dev/tty1", O_RDWR|O_NONBLOCK) = 3
fcntl(3, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl(3, F_SETFL, O_RDWR) = 0
dup2(3, 0) = 0
dup2(3, 1) = 1
dup2(3, 2) = 2
ioctl(3, TIOCSCTTY) = -1 EPERM (Operation not permitted)
brk(0) = 0x8049fdc
brk(0x804a02c) = 0x804a02c
brk(0x804b000) = 0x804b000
Cheers,
Dick Johnson
Penguin : Linux version 2.2.15 on an i686 machine (797.90 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:21 EST