Date: Tue, 29 Apr 2003 08:24:42 +1200 From: Jonathan Chen <jonc@chen.org.nz> To: "J. Seth Henry" <jshamlet@comcast.net> Cc: questions@freebsd.org Subject: Re: Odd behavior on 4.8-REL since installing KDE 3.1 Message-ID: <20030428202442.GD22360@grimoire.chen.org.nz> In-Reply-To: <20030427210629.D27080@alexandria.gambrl01.md.comcast.net> References: <20030427200729.P26560@alexandria.gambrl01.md.comcast.net> <20030427210629.D27080@alexandria.gambrl01.md.comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 27, 2003 at 09:09:32PM -0400, J. Seth Henry wrote:
[...]
> The other problem, though, is still baffling. I can't figure out what
> uptime is doing. I can understand it may be trying to read info on the
> terminal, but shouldn't it be looking at the virtual tty? Then, there is
> the strange fact that it doesn't clear after a reboot.
[...]
> > Now, when I run uptime, I get this:
> >
> > alexandria# uptime
> > uptime: /dev/dhcp0:0: No such file or directory
> > uptime: /dev/dhcp4:0: No such file or directory
> > 8:13PM up 20:41, 0 users, load averages: 0.08, 0.04, 0.01
> >
This is a problem with w(1)+uptime(1) and sessreg(1). FreeBSD's
w(1)+uptime(1) code doesn't co-exist peacefully with X11's sessreg.
The problem usually manifests itself if you're running kdm. The
Xstartup script for kdm invokes sessreg, which puts a utmp entry that
w(1)+uptime(1) doesn't like.
--
Jonathan Chen <jonc@chen.org.nz>
----------------------------------------------------------------------
"Lots of folks confuse bad management with destiny"
- Kin Hubbard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030428202442.GD22360>