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.
> vi /usr/share/gnome/apps/Utilities/gnome-terminal.desktop
>
> and change the exec line to read:
>
> Exec=gnome-terminal --utmp --wtmp
>
> This will cause all gnome-terminals (unless superceded by a local
> copy) to write to the requisite files.
Thanks for this info.
I have tried logging in/out on text console, and still no utmp.
--
Hal B
[EMAIL PROTECTED]
--
Linux helps those who help themselves
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
