Package: insserv Version: 1.11.0-8 Severity: important Hi,
I noticed a rather inconsistent behaviour of insserv. 1.) Removing runlevels from Default-Start or Default-Stop, doesn't make insserv remove the symlinks from those run levels. One has to run insserv -r $service && insserv $service This is rather cumbersome, because if you change the header file, you'd have to run insserv -r manually. I said inconsistent, because adding runlevels to Default-Start or Default-Stop will cause insserv to add new symlinks. 2.) I think there is a similar inconsistency with Required-Start. Adding new dependencies will cause insserv to update the start priority, but there are cases, if I remove a dependency, the service is not reordered (and started earlier, as early as possible). Example: powersaved # Required-Start: $remote_fs hal dbus # Required-Stop: $remote_fs hal dbus Removing hal, dbus from Required-Start # Required-Start: $remote_fs # Required-Stop: $remote_fs hal dbus and running insserv, will not make powersaved start earlier. I would have expected powersaved to be started earlier but shutdown being unchanged. Removing hal, dbus also from Required-Stop # Required-Start: $remote_fs # Required-Stop: $remote_fs will finally make insserv reorder the service, i.e. powersaved will start earlier and shutdown later. Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages insserv depends on: ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii libc6 2.7-10 GNU C Library: Shared libraries ii sysv-rc 2.86.ds1-56 System-V-like runlevel change mech insserv recommends no packages. -- debconf information: * insserv/enable: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
