Date: Tue, 4 Oct 2011 13:23:14 -0400 From: Janos Dohanics <web@3dresearch.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Timestamps shifted by 8 hours Message-ID: <20111004132314.8cc11552.web@3dresearch.com> In-Reply-To: <4E8B29FB.1050200@infracaninophile.co.uk> References: <20111004002910.4c134251.web@3dresearch.com> <4E8AC616.4000904@infracaninophile.co.uk> <20111004095026.69839e89.web@3dresearch.com> <4E8B29FB.1050200@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 04 Oct 2011 16:44:59 +0100 Matthew Seaman <m.seaman@infracaninophile.co.uk> wrote: > On 04/10/2011 14:50, Janos Dohanics wrote: > > So, I asked the wrong question. The question I should be asking is: > > Why are timestamps wrong in /var/log/filter.log even though date > > shows the correct time? However, this question I should ask the > > pfSense list... > > Hmmm... > > Somewhat of an outside chance, but timezones can be set per-process, > just by setting TZ in the environment. Make sure that procfs(5) is > mounted, and try running > > ps -auxwwwe | grep TZ Well, my pfSense installation does not have /proc, and I'd hate to mess with a production system of a customer... > If there is a process with TZ set in the environment, especially if it > is set to 'America/Los_Angeles' or similar (9 hours offset from UTC is > typical for PDT)[*] that's probably your smoking gun right there. Do > you have West Coast based users/admins who might have restarted some > processes or reloaded firewall rulesets? > > Cheers, > > Matthew > > [*] Or else on Guam or some other part of the Eastern Pacific? I'm the only one (I hope...) with access to this box... -- Janos Dohanics
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111004132314.8cc11552.web>