Matt Hyclak wrote:
On Thu, Mar 08, 2007 at 02:14:31PM -0500, Matthew Miller enlightened us:
This snippet is in order that it appears in the database. Notice the
timestamp. It starts off thinking it's almost 6pm then reverts th the
correct time of almost 10am, then to 6pm, then back to 10am and so on and
so forth. Upon looking back even further, I can see that this has been
happening as far back as the secure logs go... Early February.
Here is the root cause:
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231326>
I'm not sure what in SSH or PAM is running in GMT, though.
It has to do with the chroot. /etc/localtime doesn't get put in the chroot,
so the processes running inside the root log in GMT, outside they log in
localtime. This has been discussed on this mailing list and there is at
least one report on redhat's bugzilla.
Matt
Thanks Matts. So long as it's a known bug I'll stop worrying
something fishy is going on.
|
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
