Dennis Ferguson writes:
> And this is kind of the point.  Never calling settimeofday() is nice, but
> if the machine does manage to boot with a funky time and start processes,
> or the time is off for whatever reason, shouldn't you be able to fix it
> by calling settimeofday() without hosing things that couldn't care less about
> the time of day?

I agree. However, I think its already been dealt with -- I vaguely
recall that the kernel has some notion of a monotonically increasing
clock somewhere that doesn't get hit by time sets and is of use in
such applications -- something like mono_time is the name.

Perry