Bug#301592: chrony: [sparc] Fails to read RTC and floods logfiles

2005-04-29 Thread David S. Miller
On Fri, 29 Apr 2005 11:48:07 +0200 Frans Pop <[EMAIL PROTECTED]> wrote: > One problem is that the Mostek RTC driver currently does not support the > RTC_(RD/SET)_TIME. However, the thread contains a patch that will fix > this. I am not completely sure if this patch is final yet or if has will >

Bug#301592: chrony: [sparc] Fails to read RTC and floods logfiles

2005-04-29 Thread John Hasler
Frans Pop writes: > This issue has also been been discussed extensively on the debian-sparc > list [1]. There are some false starts in that thread, but I think this > [2] post and the thread following it contains relevant information. Thank you. I'll take a look at this. I'm probably going to ha

Bug#301592: chrony: [sparc] Fails to read RTC and floods logfiles

2005-04-29 Thread Frans Pop
Hello John, You had me confused for a bit with your very quick patched version of chrony because suddenly a default installation no longer reproduced the problems :-) This issue has also been been discussed extensively on the debian-sparc list [1]. There are some false starts in that thread, b

Bug#301592: chrony: [sparc] Fails to read RTC and floods logfiles

2005-03-27 Thread Frans Pop
This is with the default config file. It starts spewing these messages as soon as I install chrony. The problem is probably related to the fact that the system does not have an RTC or that the kernel driver for the RTC is broken. However, this is no excuse for flooding the logs in this way. IMH

Bug#301592: chrony: [sparc] Fails to read RTC and floods logfiles

2005-03-26 Thread John Hasler
Please send a copy of your config file. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#301592: chrony: [sparc] Fails to read RTC and floods logfiles

2005-03-26 Thread Frans Pop
Package: chrony Version: 1.20-6 Severity: important I have considered making this bug RC as the flood of /var/log/syslog is very severe (500 lines per second!!). This will eat diskspace in no time at all! The messages are an endless repeat of: Mar 27 01:27:57 localhost chronyd[936]: Could not sta