Package: chrony Version: 1.24-2 Severity: normal I'm also experiencing this bug. Adding "sleep 1" before pidof check works just fine.
My guess the best option would be abandoning afterwards `pidof` check, and just rely on start-stop-daemon error code, like this: if /bin/pidof $DAEMON > /dev/null then echo "$DAEMON already running." exit 1 fi if start-stop-daemon --start --verbose --exec $DAEMON then putonline else echo "$DAEMON failed to start." exit 1 fi -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-openvz-686 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages chrony depends on: ii dpkg 1.15.7.2 Debian package management system ii install-info 4.13a.dfsg.1-5 Manage installed documentation in ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii libreadline5 5.2-7 GNU readline and history libraries ii timelimit 1.6-1 Simple utility to limit a process' ii ucf 3.0025 Update Configuration File: preserv Versions of packages chrony recommends: ii udev 160-1 /dev/ and hotplug management daemo chrony suggests no packages. -- Configuration Files: /etc/init.d/chrony changed [not included] (I added "sleep 1" line) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
