>Number: 183962 >Category: bin >Synopsis: `last reboot` does not return any result >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 14 18:10:01 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Patrick Proniewski >Release: 9.2-RELEASE amd64 >Organization: >Environment: FreeBSD mydomain 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 [email protected]:/usr/obj/usr/src/sys/GENERIC amd64
>Description: The last(1) command has evolved between FreeBSD 8 and FreeBSD 9. On FreeBSD 8 issuing `last reboot` will list every reboot of the OS during current month (by default). This is done thanks to a virtual user named "reboot" used to register reboot actions into wtmp file. On FreeBSD 9, storage of these informations has moved from wtmp to a new file: utx. It looks like the pseudo-user "reboot" is no longer available in utx database, so issuing `last reboot` returns nothing : FreeBSD 8: --------------- $ last -f /var/log/wtmp.1 reboot reboot ~ Thu Sep 12 07:03 wtmp begins Mon Sep 2 09:53:18 CEST 2013 --------------- FreeBSD 9: --------------- $ last -f /var/log/utx.log.1 reboot wtmp begins Mon Sep 2 07:13:57 CEST 2013 --------------- Content of utx.log does not include proper reboot info, instead it lists shutdown and boot time: $ last -f /var/log/utx.log.1 | grep 'shut\|boot' boot time Thu Sep 12 06:40 shutdown time Thu Sep 12 06:40 user pts/1 192.168.0.2 Thu Sep 12 06:37 - shutdown (00:02) So: -1 man page is not up to date -2 last(1) source code is not up to date (still outputs "wtmp begins...") -3 would be great if `last reboot` could work like in FreeBSD 8. >How-To-Repeat: compare output of `last reboot` on FreeBSD 8 and FreeBSD 9. >Fix: >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
