Your message dated Sun, 24 Aug 2008 21:57:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line hangs when running adjtimexconfig during postinst
has caused the Debian Bug report #477637,
regarding hangs when running adjtimexconfig during postinst
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
477637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477637
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: adjtimex
Version: 1.24-1
Severity: grave
Justification: renders package uninstallable
During the postinst phase when installing this package on this laptop,
I see the message: "Comparing clocks (this will take 70 sec)..."
and then it just hangs there for hours (literally - I left it
overnight to no avail).
The same happens when I run adjtimexconfig from the command line.
I don't know what else to do to help you track down the source of this
problem.
Many thanks,
Julian
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages adjtimex depends on:
ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy
ii libc6 2.7-10 GNU C Library: Shared libraries
adjtimex recommends no packages.
-- debconf information:
* adjtimex/run_daemon: true
* adjtimex/compare_rtc: true
--- End Message ---
--- Begin Message ---
Julian Gilbey writes "a workaround would be for adjtimexconfig to wrap
its /dev/rtc read in some sort of timeout code in case the read hangs,
just as hwclock has done."
This was implemented in 1.26.
- Jim Van Zandt
--- End Message ---