1Jan 70 -- FreeBSD 5.0-RELEASE + Current

[Tim Kientzle]

This has been discussed on this list several
times:  those processes are all started
before the kernel has initialized the time.

Because FreeBSD has to read the disk
before it can know whether the hardware clock
is in UTC or local time, it's hard to really
do much better than this.  (I suppose you
could edit 'ps' to display such times
as '-'; that might be less misleading.)

Tim Kientzle

Cliff L. Biffle wrote:

> On Wednesday 23 April 2003 03:54 pm, Adrian wrote:
> 
>>EEK, Hi All
>>i'm not quite sure what to make of this but has anyone seen anything
>>similar, as its a bit of a worry. I have enclosed the following from
>>5.0-Release after having the same prob with 5.0-CURRENT-20030418 prior to
>>this the server was running 4.5-Release-p2 and it was ok.
>>
> 
> I get the 1Jan70 process ages as well.  While a bit unusual, I don't believe 
> it's problematic; all the processes with that date are kernel-related or 
> low-level system processes.  1Jan70 just means their start dates are zero.
> 
> This strikes me as a bug, yes, but probably not fatal. :-)
> 
> -Cliff L. Biffle
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> 
> 
>