There is a bug in all Squid-2.2 and earlier versions relating to
the end of the year. This bug, in the mkhttpdlogtime() function,
causes timezone offsets to be printed incorrectly. You should
probably apply the patch if you use any of these options:
* the "common" logfile format for access.log, which is
enabled with 'emulate_httpd_log' option in squid.conf.
* the useragent.log, which is enabled with the
'useragent_log' option in squid.conf.
Installations that use the normal access.log format, and don't
use useragent.log, do not need to worry about this bug.
Also, the bug probably only occurs for less than 24 hours on the
first day of the new year.
The patch is available from the top of the version 2.2 bugs page:
http://www.squid-cache.org/Versions/v2/2.2/bugs/
NOTE: if you use one of Henrik's snapshots, then you probably
don't need to apply this patch. Henrik submitted this patch
many months ago and I applied it to the 2.3 branch, but failed to
apply it to the 2.2 branch.
Duane W.
> There is a bug in all Squid-2.2 and earlier versions relating to the end
> of the year.
NOW you tell us! ;-)
> Installations that use the normal access.log format, and don't
> use useragent.log, do not need to worry about this bug.
Thank goodness for that. Squid 2.2.STABLE5 still humming along nicely through
the rollover...
dave
> Also, the bug probably only occurs for less than 24 hours on the
> first day of the new year.
It appears the 24 hours around new year only, and as Duane said it only
affects logging using common time format. It should be safe by now up
till next new year.
> NOTE: if you use one of Henrik's snapshots, then you probably
> don't need to apply this patch.
True. The patch has been in my snapshots as long as 2.2 has been
released as STABLE (excluding DEVEL/PRE versions).
/Henrik
> > There is a bug in all Squid-2.2 and earlier versions relating to
> > the end of the year.
>
> NOW you tell us! ;-)
And none of the users Y2K auditing Squid noticed it it seems... Not that
it strictly speakins is a Y2K bug, it is a new year bug seen a few hours
every new year while local time and GMT are in different years... I
noticed the bug by accidently 8 of april while reading the sources, and
a patch was released shortly after that. Has been posted on my patches
page since then..
/Henrik