I'm using a FreeBSD 5 x86 system.
I have no users aside from root and my normal login, ie. the computer is not used by anyone other than myself.
I find that I get two ghosted logins after running KDE. These logins have no processes attached to them and `who` reports that they came from my eth0 hostname. They appear on ttyp0 and p1. I've tried to `watch -W ttyp0` but Watch is unable to write to the tty; which makes sense because the ttys are not actually logged in. I can remedy the problem by logging out of KDE, closing any local shells, v0, v1, etc. then SSHing into the box twice and using logout. After that the shells seem to get the hint and get reported as logged out. So far it's not a security issue, it seems more an annoyance than anything, but I fear it may suggest a problem with my computer's configuration. /var/run/utmp is set to rw-r-r, as is /var/log/wtmp. From what I've read here and in the man pages that is the appropriate setting.
Is this a problem with file permissions or is it a KDE/Xwin problem? Or is it something else all together?
update:
here is some additional information...
I logged out p0 (using login from SSH) and took a look at /dev, here is p0 and p1. right now p1 is still logged in according to `who`
Quote:
crw-rw-rw- 1 root tty 5, 0 Dec 2 11:08 ttyp0
crw-r--r-- 1 root tty 5, 1 Dec 1 15:58 ttyp1
I kind of understand the concept behind entries in /dev, but not enough to think that I could change file settings arbitrarily.
Thank you,
-John
The solution to this is such:
Quote:
This is an inherant bug with KDE's handleing of FreeBSD terminals via `konsole_grantpty`. It was fixed in more recent versions of KDE, there are also several amature patches avaialble, however there is no non-patch fix for FreeBSD 5-REL/KDE 3. The patches require a complete reinstallation of KDE, and in most cases are just not worth the effort.
I've chosed to ignore it.
