Your message dated Wed, 6 May 2009 17:57:12 +0200
with message-id <20090506155711.ga10...@pc23>
and subject line Re: Bug#515088: chrony: Chrony suddenly starts eating a whole
CPU
has caused the Debian Bug report #515088,
regarding chrony: Chrony suddenly starts eating a whole CPU
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.)
--
515088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515088
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.23-6
Severity: important
Hi,
this problem *might* be related to #474294. After running for a while chrony
sporadically starts eating a whole CPU. I'm running inside a VMWare virtual
machine. No, I can't really tell how long it takes until the problem occurs.
Thanks,
Hilmar
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages chrony depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libreadline5 5.2-3.1 GNU readline and history libraries
ii timelimit 1.4-1 Simple utility to limit a process'
ii ucf 3.0016 Update Configuration File: preserv
Versions of packages chrony recommends:
ii udev 0.125-7 /dev/ and hotplug management daemo
chrony suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 06.03.09 John Hasler ([email protected]) wrote:
Hi John,
> Can you reproduce this outside VMWare?
>
Sorry for the late response. I don't have an unstable box running an
non-vitual hardware, hence I can't answer your question. However I
observed the CPU utilization of the system for a weeks now and the
problem did not re-occur. Hence I close this bug.
Sorry for the noise!
Hilmar
--
sigmentation fault
--- End Message ---
