On Sat, Dec 25, 1999 at 12:08:41PM -0500, Hal Burgiss wrote:
> On Sat, Dec 25, 1999 at 08:43:29AM -0800, Todd A. Jacobs wrote:
> > On Sat, 25 Dec 1999, Hal Burgiss wrote:
> >
> > > I've started getting 'cannot determine runlevel' errors from daily
> > > cron. I find there is a 'runlevel' command that reads utmp, but cannot
> > > find where in the cron runs this is getting called. I also find there
> > > is no 'utmp'.
> >
> > October GNOME and later default gnome-terminal to NOT write to utmp and
> > wtmp for some strange reason. If you're booting into runlevel 5, you may
> > not have any recorded logins, so of course you won't get anything useful
> > out of utmp or wtmp.
>
> Thanks for response. But I am not running gnome. I am booting runlevel
> 5 for some time now, and just started getting these messages yesterday
> (mailed to root from cron run).
>
> > First, delete any copies of utmp or wtmp on your system; they may be
> > corrupt. Second, do the following:
>
> utmp has been deleted for me ;) It is not there, and it *was* there.
> wtmp is still there.
[...]
OK, for anyone interested, the missing file was actually
/var/run/utmp. Recreated this as per rc.sysinit and all is well again.
PBKAC, ie momentary $USER idiocy.
--
Hal B
[EMAIL PROTECTED]
--
Linux helps those who help themselves
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
