Package: chrony Version: 1.23-3 Severity: important After upgrading from linux-image-2.6-686/2.6.25+14 to linux-image-2.6-686/2.6.26+15, my system refused to boot, stopping at the chrony daemon starting step.
I had to reboot with the previous (2.6.25) linux kernel image, disable chrony for my runlevel and reboot with the new (2.6.26) kernel, in order to investigate. It turned out that the RTC device is no longer /dev/rtc , but apparently /dev/rtc0 . Adding the following lines to /etc/chrony/chrony.conf # This directive defines the name of the device file for # accessing the real time clock. By default this is `/dev/rtc/', unless # the directive is used to set a different value. rtcdevice /dev/rtc0 fixed the issue. I think that something should be done, in order to save other users from this bad surprise. I set the severity of this bug to important, but it could be considered worse than that, because it could prevent system boot in some circumstances... -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages chrony depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libreadline5 5.2-3 GNU readline and history libraries ii ucf 3.007 Update Configuration File: preserv chrony recommends no packages. chrony suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
