<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 227: timezone support in BASE spotty?</title><link href="https://sourceforge.net/p/secureideas/bugs/227/" rel="alternate"/><link href="https://sourceforge.net/p/secureideas/bugs/227/feed.atom" rel="self"/><id>https://sourceforge.net/p/secureideas/bugs/227/</id><updated>2009-10-09T18:44:56Z</updated><subtitle>Recent changes to 227: timezone support in BASE spotty?</subtitle><entry><title>timezone support in BASE spotty?</title><link href="https://sourceforge.net/p/secureideas/bugs/227/" rel="alternate"/><published>2009-10-09T18:44:56Z</published><updated>2009-10-09T18:44:56Z</updated><author><name>Jason Haar</name><uri>https://sourceforge.net/u/jhaar/</uri></author><id>https://sourceforge.net9c95f638b313f641bc85d444e80518b66844a3d4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi there&lt;/p&gt;
&lt;p&gt;We're running several snort sensors in different countries, so we run all the collectors in UTC. However, we'd like the different base frontends to show time in local time. We ensure "TZ" is set correctly and sure enough, when you enter base, "Queried on" returns the current time in the local timezone - but all the times associated with snort events are still in UTC. I'm guessing that is because the former does direct PHP time calls (and is affected by TZ) whereas the snort events come out of mysql - and are not.&lt;/p&gt;
&lt;p&gt;mysql enables you to change the timezone settings via " SET time_zone =  'Pacific/Auckland';" (assuming you've initialized mysql tables correctly). Could support for that be added to base?&lt;/p&gt;
&lt;p&gt;Perhaps something like&lt;/p&gt;
&lt;p&gt;if (!preg_match("/^$/",getenv("TZ")) { dbcall "SET time_zone =  getenv("TZ");"}&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Jason&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>