On Sun, Dec 20, 2015 at 6:06 PM, Duncan Patton a Campbell <[email protected]> wrote: > On Sun, 20 Dec 2015 12:37:30 -0800 > Philip Guenther <[email protected]> wrote: > >> On Sat, Dec 19, 2015 at 3:31 PM, Duncan Patton a Campbell >> <[email protected]> wrote: >> > I've a question about last/utmp/wtmp that someone here should be >> > able to answer. >> > >> > At the shell I do >> > >> > # date >> > Sat Dec 19 16:29:07 MST 2015 >> > # last >> > >> > wtmp begins Sat Dec 19 16:29 2015 >> > >> > This appears to set the beginning time to "now" >> > every time I run the thing. WTF sets the >> > lower bound so as to see back from "now"? >> > >> > It is not exactly obvious from the man pages how this works. >> > I'm sure it's there, I just can't find it. >> >> Well, you apparently know that the data comes from /var/log/wtmp, so >> what's the status of that file? It should be a normal file of >> non-zero length. If it's a symlink to /dev/null or something bogus >> then you need to figure out why and maybe reinstall from scratch. > > # ls -l /var/log/wtmp > - -rw-r--r-- 1 root wheel 0 Dec 19 04:00 /var/log/wtmp
(Not sure why there's that extra '- ' at the beginning of that. Did your email client quote it?) So, the file isn't growing. Why? Is the filesystem full? Is /var not mounted read-write? >> Also, you failed to include the dmesg or even mention what version >> you're running, so maybe we should just go with "you're clearly >> running an out of date version and probably screwed up an upgrade >> across the time_t size change"... > > I'm running 5.7 dmesg as follows: > > OpenBSD 5.7 (GENERIC.MP) #881: Sun Mar 8 11:04:17 MDT 2015 > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP Good; not a known problem in that release. (Hmm, -current might run cooler since kettenis enabled some deeper mwait bits on AMD CPUs after 5.8 was released, iirc.) Philip Guenther
