Hi,
I forgot when I noticed this curious problem... It's not so serious
but annoying. Any help is appreciated.
Situation:
1. Running 4.0-current. Uname -a says
FreeBSD xa12.heimat.gr.jp 4.0-CURRENT FreeBSD 4.0-CURRENT #8: Sat
Mar 4 22:36:09 JST 2000
[EMAIL PROTECTED]:/export/src/sys/compile/NAKAJI i386
The system is upgraded by making world from 3.1-RELEASE.
2. XFree86 3.3.6 compiled by ports/x11/XFree86.
3. Xserver is X-TT.
4. Login via XDM and using sessreg to record logins into utmp.
/usr/X11R6/lib/X11/xdm/GiveConsole is:
chown $LOGNAME /dev/console
sessreg -a -l $DISPLAY -x /usr/X11R6/lib/X11/xdm/Xservers $LOGNAME
if [ -f /var/run/xdm.pids ]; then
kill `cat /var/run/xdm.pids`
rm -f /var/run/xdm.pids
fi
/usr/X11R6/lib/X11/xdm/TakeConsole is:
/usr/X11R6/bin/sessreg -d -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME
chmod 622 /dev/console
chown root /dev/console
Problems:
1. w, uptime and finger complains about non-existence of /dev/:0, for
example,
$ w
w: /dev/:0: No such file or directory
10:41PM up 29 mins, 1 user, load averages: 0.00, 0.08, 0.23
USER TTY FROM LOGIN@ IDLE WHAT
nakaji p1 :0.0 10:32PM - w
2. 'sessreg -d' does not record my logout (the user is only me), that
is,
$ LC_TIME=C last | head
nakaji :0 console Tue Mar 7 22:31 still logged in
nakaji :0 console Tue Mar 7 22:22 still logged in
nakaji :0 console Tue Mar 7 22:13 still logged in
Until rebooting the system, I am always loging in on /dev/:0.
Questions:
1. Why w and so on complain, "/dev/:0: No such file or directory"?
(Why /dev/:0 is to be opened?)
2. Is my usage of sessreg wrong?
Thanks in advance.
--
NAKAJI Hiroyuki
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message