At work, we have noticed that sometimes xxgdb failed opening ttypX due to lack
of permissions giving something like "/dev/ttypX : Permission denied".
To cut a long story short, what we think to have found is that by telnetting
(rlogin causes it also) to the machine, and then disconnecting, the pseudo tty
file permissions aren't correctly restored.
For instance :
BEFORE TELNETTING ...
[root@localhost campedel]# ls -Fla /dev/ttyp3
crw-rw-rw- 1 root tty 3, 3 Aug 2 1996 /dev/ttyp3
[root@localhost campedel]# telnet localhost
...
[campedel@localhost campedel]$ exit
AFTER TELNETTING ...
[root@localhost campedel]# ls -Fla /dev/ttyp3
crw------- 1 root root 3, 3 May 1 14:11 /dev/ttyp3
And then, in this situation, if xxgdb (or a program not running root anyway)
opens /dev/ttyp3 fails.
This happens consistently with Kernels 2.0.3[023] on RH4.2 and RH5.0, but not
with Kernel 2.0.33 on Slackware, so hardly is a kernel problem.
Thanks for your time.
Lorenzo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu