🚀 go-pugleaf

In article <1992Oct9.031609.11958@dartvax.dartmouth.edu>
	fermat@fermat.dartmouth.edu (Michael Glenn)
>What does this mean, in my /tmp/console.log file.
>
>Software Version 3.0 (Hyper3B)
>opening /usr/adm/lastlog: Bad file number
>opening /etc/utmp: Bad file number
>opening /usr/adm/wtmp: Bad file number
>opening /etc/utmp: Bad file number
>opening /usr/adm/wtmp: Bad file number
>
>This only showed up yesterday, and I've been running 3.0 for over
>a couple of weeks.  What have I done?

You're using Stuart2.4 with the slog facility incorrectly installed.
The first three "opening" lines are from when you brought up a new
window, the last two from when you closed it (lastlog is only logged
on open).  They shouldn't be printing out "Bad file number", but
there's a slight bug in slog's lopen() procedure that causes it to
attempt an flock() even when the open() failed, and since the fd
is -1, you get what you're seeing.

There's a New Improved Correctly-Logging Version of slog available
on request - but, the problem will _most_ likely come down to not
having installed slog setuid-root.  Give the installation instructions
a re-read and see if that fixes things.  You should see something like:

howard:/tmp> ls -lg ~/Apps/Stuart.app/slog
-rwsr-sr-x   1 root     tty         32768 Oct  5 22:47 /Users/scott/Apps/Stuart.app/slog*

With the "-rws-sr-x" being the operative segment.

Later,
--
scott hess <shess@ssesco.com>     <I will not spin the turtle -Bart Simpson>
12901 Upton Avenue South, #326  Burnsville, MN 55337 (612) 895-1208 Anytime!
  * ... like a big church choir with all it's members' mouths wide open, *
               * singing silence   -Blood Music, Greg Bear *