>On Fri, Jul 8, 2011 at 4:26 PM, Vick Khera <[email protected]> wrote: >> On Fri, Jul 8, 2011 at 1:06 PM, Dimitri Rodis >> <[email protected]> wrote: >>> >>> I have my log set to show newest on top, and the log is "mostly" in >>> order, but notice how there are some entries that are in the middle >>> of this screenshot that are "newer" than everything else. (The >>> problem is that Jul 8 >>> 15:12:29 has not yet happened in my time zone, it is only shortly >>> after 10AM >>> here..) >> >> What's your offset to GMT? I'll guess +5 If the process started >> before the timezone was set, then you will see stuff like this. Same >> if you alter the timezone after the process is started. >> They do not re-read the timezone file ever. >> > >This. If you want everything to be on the right timezone you have to reboot >after setting it (or restart the services individually), that's always been >the case. The logs show in the order they were >logged, with the timestamp of >the process doing the logging. > >---------------------------------------------------------------------
The system is and has been set to -8 (I am Pacific Daylight Time, USA), and hasn't been re/booted since the first boot on that build--and I have reported this issue back in RC1 and it still appears to be an issue. It almost looks as if the check_reload_status (among a couple of others that haven't shown up in the log yet) specifically always logs with the wrong timestamp. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
