> I am not sure whether the TZ variable is being set on the execution
> of the rotatelogs script that is spawned from the httpd.
I don't think it has any effect without -l, since the date in the
filename would be UTC.
-
The offic
You would assume so, but the guidance in the documentation says the
following:
"Causes the use of local time rather than GMT as the base for the interval
or for strftime(3) formatting with size-based rotation. Note that
using -lin an environment which changes the GMT offset (such as for
BST or DST
> My concern is though that when we switch back to GMT in October that i will
> then have to remove the "+60" from the configuration.
Isn't that what -l does for you?
-
The official User-To-User support forum of the Apache HTTP S
hi rob,
we do have summers, they just don't last very long!!!
Yes normally its started from a startup script and we do specify a TZ
variable, which i've got a feeling is not correct. I'll look into this.
cheers
Steve
On Wed, Apr 6, 2011 at 1:20 PM, Rob De Langhe wrote:
> hey Steve,
>
> didn't
hey Steve,
didn't know you guys have summers in Britain ?! ;-)
I would guess your Apache is started either from CRON or in any case from a
startup script that didn't have the right TZ environment variable set.
Rob
Citeren Steve Foster :
> Hi there,
>
> I have a slight issue with rota
Hi there,
I have a slight issue with rotatelogs and british summer and wintertime.
When in BST my logfile entries are being written with the correct timestamp
(localised) but the logfile rotation filename does not match the current
time,
e.g i set my logfile name as
/opt/app/apache2.2.17/logs/st
