Re: 2007 DST changes, and a "non-issue" statement...
On 1/26/07, Nick Kew <[EMAIL PROTECTED]> wrote: > >> Apache httpd and bundled libraries do not maintain their own time > >> zone information. Instead, information is retrieved from the > >> operating system. Relevant operating system updates must be > >> applied and the web server restarted to prevent potential time > >> display problems with logging and server-generated reports. > >> > >> Web applications and third-party modules and libraries used with > >> the web server must be investigated separately. How about replacing "must" with "may have to be"? We're not in the business of saying someone else is guilty, only that we're innocent. Either way works for me. Is it a quick task for somebody on this thread to post it on the news page? Its definitely news right now, but we might want to put it in the FAQ for long-term, as surely this will come up again.
Re: 2007 DST changes, and a "non-issue" statement...
> >> Apache httpd and bundled libraries do not maintain their own time > >> zone information. Instead, information is retrieved from the > >> operating system. Relevant operating system updates must be > >> applied and the web server restarted to prevent potential time > >> display problems with logging and server-generated reports. > >> > >> Web applications and third-party modules and libraries used with > >> the web server must be investigated separately. How about replacing "must" with "may have to be"? We're not in the business of saying someone else is guilty, only that we're innocent. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/
Re: 2007 DST changes, and a "non-issue" statement...
Jim Jagielski wrote: > Jeff Trawick wrote: >> Is there anything to say other than (for httpd, for example): >> >> Apache httpd and bundled libraries do not maintain their own time zone >> information. Instead, information is retrieved from the operating >> system. Relevant operating system updates must be applied and the web >> server restarted to prevent potential time display problems with >> logging and server-generated reports. >> >> Web applications and third-party modules and libraries used with the >> web server must be investigated separately. >> > > +1 +1 - is this one for the main news page at httpd.apache.org and apr.apache.org? The short and to-the-point style would fit nicely :)
Re: 2007 DST changes, and a "non-issue" statement...
Jeff Trawick wrote: > > Is there anything to say other than (for httpd, for example): > > Apache httpd and bundled libraries do not maintain their own time zone > information. Instead, information is retrieved from the operating > system. Relevant operating system updates must be applied and the web > server restarted to prevent potential time display problems with > logging and server-generated reports. > > Web applications and third-party modules and libraries used with the > web server must be investigated separately. > +1 -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
Re: 2007 DST changes, and a "non-issue" statement...
On 1/25/07, Jim Jagielski <[EMAIL PROTECTED]> wrote: We did it with Y2K so +1... Is there anything to say other than (for httpd, for example): Apache httpd and bundled libraries do not maintain their own time zone information. Instead, information is retrieved from the operating system. Relevant operating system updates must be applied and the web server restarted to prevent potential time display problems with logging and server-generated reports. Web applications and third-party modules and libraries used with the web server must be investigated separately.
Re: 2007 DST changes, and a "non-issue" statement...
On Jan 24, 2007, at 6:43 PM, Colm MacCarthaigh wrote: On Wed, Jan 24, 2007 at 05:28:49PM -0500, Victor J. Orlikowski wrote: I've been getting some questions (from my new employer) on the impact of the upcoming Daylight Saving Time issues for the httpd. My natural response was: "There are none! It's an OS issue." Whatever about DST, this reminds me that there may actually be some real problems in our code with negative leap seconds, and there is still a chance there will be a negative leap second in late 2007. We have a few code-paths that will fail for that I think (like trying to calculate bandwidth rates, or times of downloads and so on). Good point!
Re: 2007 DST changes, and a "non-issue" statement...
We did it with Y2K so +1... I've been seeing a *huge* increase in these questions as well. On Jan 24, 2007, at 5:28 PM, Victor J. Orlikowski wrote: Long time, no speak on my behalf. I hope to be changing that soon. So - to de-cloak: I've been getting some questions (from my new employer) on the impact of the upcoming Daylight Saving Time issues for the httpd. My natural response was: "There are none! It's an OS issue." Whereupon, I was told that upper management would prefer to have something rather more "official" than my word on it. So - suspecting that this might become something of a FAQ in the coming months, I figured that it might be helpful to post something to the httpd site on the (non)impact to httpd/apr, if only to save headaches. Thoughts? Thanks, Victor -- Victor J. Orlikowski <> [EMAIL PROTECTED]
Re: 2007 DST changes, and a "non-issue" statement...
On Wed, Jan 24, 2007 at 05:28:49PM -0500, Victor J. Orlikowski wrote: > I've been getting some questions (from my new employer) on the > impact of the upcoming Daylight Saving Time issues for the httpd. > > My natural response was: "There are none! It's an OS issue." Whatever about DST, this reminds me that there may actually be some real problems in our code with negative leap seconds, and there is still a chance there will be a negative leap second in late 2007. We have a few code-paths that will fail for that I think (like trying to calculate bandwidth rates, or times of downloads and so on). -- Colm MacCárthaighPublic Key: [EMAIL PROTECTED]
Re: 2007 DST changes, and a "non-issue" statement...
Victor J. Orlikowski wrote: > > Whereupon, I was told that upper management would prefer to have > something rather more "official" than my word on it. Ok, you offer them one :) ASF projects make no warranties. If you want to dredge up the old Y2K comments from the site svn history it's probably trivial to change a few words.
