Bug 86803

Summary:	sys-apps/sysvinit last -x outputs incorrect down time duration
Product:	Gentoo Linux	Reporter:	Dmitry Karasik <dkarasik>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	proposed fix

Description Dmitry Karasik 2005-03-26 14:27:56 UTC

The down time displayed is the downtime + following uptime

Reproducible: Always
Steps to Reproduce:
1. run last -x
2.
3.

Actual Results:  
sample output:
reboot   system boot  2.6.10-gentoo-r6 Thu Mar 17 16:50          (19:40)
shutdown system down  2.6.10-gentoo-r6 Thu Mar 17 16:46 - 12:31  (19:44)


Expected Results:  
reboot   system boot  2.6.10-gentoo-r6 Thu Mar 17 16:50          (19:40)
shutdown system down  2.6.10-gentoo-r6 Thu Mar 17 16:46 - 16:50  (00:04)

Comment 1 Dmitry Karasik 2005-03-26 14:29:16 UTC

Created attachment 54547 [details, diff]
proposed fix

Comment 2 SpanKY gentoo-dev

2005-03-28 21:18:37 UTC

maybe it's me but that patch doesnt seem to work right ...

before:
root     tty1                          Mon Mar 21 20:19   still logged in   
runlevel (to lvl 3)   2.6.12-rc1       Mon Mar 21 15:21 - 00:11 (7+08:49)   
reboot   system boot  2.6.12-rc1       Mon Mar 21 15:21         (7+08:49)   
shutdown system down  2.6.11           Mon Mar 21 18:07 - 00:11 (7+06:03)   
runlevel (to lvl 0)   2.6.11           Mon Mar 21 18:07 - 18:07  (00:00)    

after:
root     tty1                          Mon Mar 21 20:19   still logged in   
runlevel (to lvl 3)   2.6.12-rc1       Mon Mar 21 15:21 - 00:18 (7+08:57)   
reboot   system boot  2.6.12-rc1       Mon Mar 21 15:21         (7+08:57)   
shutdown system down  2.6.11           Mon Mar 21 18:07 - 15:21  (-2:-45)   
runlevel (to lvl 0)   2.6.11           Mon Mar 21 18:07 - 18:07  (00:00)

Comment 3 Dmitry Karasik 2005-03-29 06:21:58 UTC

it seems your system went down at 18:07 and then went up at 15:21 on the same day, so the output is correct, it is your system clock that is messed up.

Comment 4 Dmitry Karasik 2007-08-09 20:34:30 UTC

How does this work for you? With 2.86-r8 I am still seeing the same behaviour.