Bug#647884: cron wrong time in logs

2023-08-27 Thread Georges Khaznadar
Hi, this bug report is now twelve years old. Christian Kastner asked for
a snippet of a log file, which was not sent, and explained that this
kind of bug is now fixed in recent versions of cron.

So, I clode this bug report.

Best regards,   Georges.

Christian Kastner a écrit :
> severity 647884 normal
> thanks
> 
> Hi,
> 
> On 2011-11-07 10:34, Serguei wrote:
> > Package: cron
> > Version: 3.0pl1-116
> > Severity: critical
> ^^^
> Bug severities have a very specific meaning in Debian, see
> 
> http://www.debian.org/Bugs/Developer#severities
> 
> I'm downgrading this to "normal" according to said policy.
> 
> > i have timezone /etc/timezone which is equal to Europe/Moscow. After 29
> > october When all world moved clock to winter time our timezone left on
> > summer time.
> > 
> > first problem: cron runs task as scheduled but puts time into syslog
> > with timeshift minus 1 hour
> 
> cron does not specify any time at all -- the timestamp in syslog comes
> from the syslog daemon. So whatever the problem is, it can only be
> resolved there.
> 
> Could you post a short snippet of your log file with a valid entry
> shortly before the DST change and the first invalid entry?
> 
> > second problem: each time crontab file changes cron daemon must be
> > restarted to reread crontab
> 
> This issue (previously reported as #625495 and #627859) has been
> resolved in package version 3.0pl1-117.
> 
> 
> Christian
> 



-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature


Bug#647884: cron wrong time in logs

2011-11-12 Thread Christian Kastner
severity 647884 normal
thanks

Hi,

On 2011-11-07 10:34, Serguei wrote:
 Package: cron
 Version: 3.0pl1-116
 Severity: critical
^^^
Bug severities have a very specific meaning in Debian, see

http://www.debian.org/Bugs/Developer#severities

I'm downgrading this to normal according to said policy.

 i have timezone /etc/timezone which is equal to Europe/Moscow. After 29
 october When all world moved clock to winter time our timezone left on
 summer time.
 
 first problem: cron runs task as scheduled but puts time into syslog
 with timeshift minus 1 hour

cron does not specify any time at all -- the timestamp in syslog comes
from the syslog daemon. So whatever the problem is, it can only be
resolved there.

Could you post a short snippet of your log file with a valid entry
shortly before the DST change and the first invalid entry?

 second problem: each time crontab file changes cron daemon must be
 restarted to reread crontab

This issue (previously reported as #625495 and #627859) has been
resolved in package version 3.0pl1-117.


Christian



signature.asc
Description: OpenPGP digital signature


Bug#647884: cron wrong time in logs

2011-11-07 Thread Serguei

Package: cron
Version: 3.0pl1-116
Severity: critical

i have timezone /etc/timezone which is equal to Europe/Moscow. After 29 
october When all world moved clock to winter time our timezone left on 
summer time.


first problem: cron runs task as scheduled but puts time into syslog 
with timeshift minus 1 hour
second problem: each time crontab file changes cron daemon must be 
restarted to reread crontab






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org