From owner-freebsd-commit  Sat Nov 18 21:36:54 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA14333
          for freebsd-commit-outgoing; Sat, 18 Nov 1995 21:36:54 -0800
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA14273
          for cvs-all-outgoing; Sat, 18 Nov 1995 21:35:28 -0800
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA14263
          for cvs-usrbin-outgoing; Sat, 18 Nov 1995 21:35:24 -0800
Received: (from wpaul@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA14170
          ; Sat, 18 Nov 1995 21:33:39 -0800
Date: Sat, 18 Nov 1995 21:33:39 -0800
From: Bill Paul <wpaul>
Message-Id: <199511190533.VAA14170@freefall.freebsd.org>
To: CVS-commiters, cvs-usrbin
Subject: cvs commit: src/usr.bin/rup rup.c
Sender: owner-commit@FreeBSD.ORG
Precedence: bulk

wpaul       95/11/18 21:33:36

  Modified:    usr.bin/rup  rup.c
  Log:
  Rup uses tm_yday in its uptime printout, but ignores tm_year. This means
  that if you do an rup on a machine that's been running longer than a year,
  you get the wrong day count. Now we factor in 365 * (curtime.tm_year -
  boottime.tm_year) to get the correct value. (I noticed this while running
  rup on a SunOS machine I have that's been up 525 days. My FreeBSD
  machines all said it had only been up for 160 (525-365) days. :)