At Sat, 22 Jan 2011 19:49:18 -0800 CentOS mailing list <centos at centos.org> wrote: > > On Sat, Jan 22, 2011 at 7:06 PM, Robert Heller <heller at deepsoft.com> wrote: > > At Sat, 22 Jan 2011 21:40:57 -0500 CentOS mailing list <centos at centos.org> wrote: > > > >> > >> Hello list! > >> > >>  I was just curious about the output of a command I typed. > >> > >> [root at LCENT02:~] #last reboot | head -1 > >> reboot  system boot  2.6.18-194.26.1. Wed Dec 29 20:03     (24+01:33) > >> > >> > >> This is odd because this machine was rebuilt today (Saturday 1/22) in > >> mid afternoon. Just curious how the output of this command could NOT > >> know this? > > > > What was the hw clock set to on reboot? > > > > When it's almost a month off, is this really relevant? I could see a > timezone discrepancy making this relevant, maybe, but not three weeks. Unless the hardware clock was off for some reason (dead/weak BIOS battery?). If you are running ntpd, it will sync up pretty quick, but if the clock is wrong at boot time, that is what will be recorded in the last database. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > -- Robert Heller -- 978-544-6933 / heller at deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments