Re: XDM login using sessreg and last, uptime, w and so on...

2000-03-09 Thread NAKAJI Hiroyuki

 In [EMAIL PROTECTED] 
   "Sean O'Connell" [EMAIL PROTECTED] wrote:

 On FreeBSD it was successful and there seems no problem.
Sean One out of two is not bad :)

I think so too. :-)

Sean Could your path be set in such a way that it is exec'ing 3.X
Sean versions of fileutils or finger or something like that in 
Sean /usr/local/bin rather than updated ones in /usr hierarchy.

No. These tools are all in /usr/bin.

Sean Did you run mergemaster on /etc and/or update all the various
Sean rc files?

Yes. I have just run mergemaster and reboot the system.

Sean The /usr/X11R6/bin/X symlink really points to an updated
Sean XF86_ like you didn't switch for using XF86_S3 to XF86_SVGA
Sean (only built this) but the symlink for X is still pointing to
Sean XF86_S3.

I'm using X-TT server on both FreeBSD and FreeBSD(98). This morning, I
recompiled X-TT of FreeBSD(98) and there still is 'w: /dev/:0: No such
file or directory'. X is properly linked to XF98_MGA.xtt.

Sean Curious... love a good mystery.

Yes, this is a mystery but not so serious...

Ok, I'll ask about this problem to FreeBSD(98)'s mailing list. It
may be pc98's problem...

Thank you all very much for your help.
-- 
NAKAJI Hiroyuki


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



XDM login using sessreg and last, uptime, w and so on...

2000-03-07 Thread NAKAJI Hiroyuki

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



Re: XDM login using sessreg and last, uptime, w and so on...

2000-03-07 Thread NAKAJI Hiroyuki

 In [EMAIL PROTECTED] 
   Jose Marques [EMAIL PROTECTED] wrote:

Jose  /usr/X11R6/lib/X11/xdm/TakeConsole is:
Jose  
Jose  /usr/X11R6/bin/sessreg -d -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME
Jose   ^^^
Jose Missing X11 in path?

Ah... Thank you very much!

One problem is solved but another '/dev/:0' problem still remains.

$ w
w: /dev/:0: No such file or directory
 7:15AM  up  9:04, 1 user, load averages: 0.31, 0.15, 0.06
USER TTY  FROM  LOGIN@  IDLE WHAT
nakaji   p1   :0.0  7:15AM - w
$ last | head
nakaji   :0   console  Wed Mar  8 07:15   still logged in
nakaji   :0   console  Wed Mar  8 07:11 - 07:15  (00:03)
-- 
NAKAJI Hiroyuki


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message