These applications run 24/7 and obviously wrote to the log files
before the clocks went back. Once they did though the applications
died.
When this happened last year we changed mosts of the logs over from
daily to weekly which got round the problem. But some logs do need to
be rotated daily. Is there any way to fix this so that I don’t have to
go round checking out the world and it’s dog next year?
When this happened last year we changed mosts of the logs over from
daily to weekly which got round the problem. But some logs do need to
be rotated daily. Is there any way to fix this so that I don’t have to
go round checking out the world and it’s dog next year?
can you add the timezone information to the logfilename?
I’m pretty sure that our server are running local time and not UTC
(which would be a sure fix - I think). Not really sure that I would
feel confident changing to UTC for nearly a dozen servers located on
two continents.
Are your servers running local clocks or UTC? We’re shifting next
week and I hadn’t anticipated a problem but now that you bring it up I
wonder if I’ve missed something. Our servers are running UTC.
I’m pretty sure that our server are running local time and not UTC
(which would be a sure fix - I think).
Ok. Thanks.
Not really sure that I would feel confident changing to UTC for nearly a dozen
servers located on two continents.
You have a knack for understatement At a minimum it would wreak
havoc with your reporting apps which invariably use the system
date/time to grab the ‘right’ records.
Best regards,
Bill
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
At a minimum it would wreak