Description of problem: /usr/bin/uptime does not properly handle large numbers. How can someone promote and publicize a high uptime when reporting utility is incorrect? Version-Release number of selected component (if applicable): procps-2.0.11-6 How reproducible: ALWAYS Steps to Reproduce: 1. Boot Linux system 2. Go away for 497 days 3. check uptime Actual results: [root@utility OLD]# uptime 15:59:01 up 23 days, 23:08, 6 users, load average: 0.10, 0.13, 0.09 Expected results: [root@utility OLD]# uptime 15:59:01 up 520 days, 23:08, 6 users, load average: 0.10, 0.13, 0.09 Additional info: 05/19/03 00:00:00 up 495 days, 9:32, 4 users, load average: 0.04, 0.06, 0.06 05/20/03 00:00:00 up 496 days, 9:32, 4 users, load average: 0.06, 0.11, 0.09 05/21/03 00:00:00 up 7:05, 4 users, load average: 1.14, 1.17, 1.17 05/22/03 00:00:00 up 1 day, 7:05, 4 users, load average: 1.19, 1.29, 1.27 05/23/03 00:00:01 up 2 days, 7:05, 4 users, load average: 1.13, 1.25, 1.27 [root@utility OLD]# cat /proc/uptime 2070689.03 41047961.72
This is a kernel problem. Uptime is basically jiffies, and at 100 Hz it wraps in 497 days
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/
Looks like this fell off the cracks and has not been fixed yet. http://www.linux-noob.com/forums/index.php?showtopic=1780
that report is against fc1 which was 2.4 based. all 2.6 kernels have this fixed.