Package: wajig Version: 2.0.36 Severity: normal At present, wajig uses `invoke-rc.d' to control /etc/init.d/ scripts. But `invoke-rc.d' is supposed to use by package(such as those scripts) maintainers, who decide on which runlevel the server could start/stop. For the users, one should use /etc/init.d/* start/stop/... directly, which is the more reliable way.
For instance, recently i found tinyproxy isn't configured to start(by default) in all runlevels. Because of this, `wajig start tinyproxy' won't work at all. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.21 Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to zh_CN.utf-8) Shell: /bin/sh linked to /bin/bash Versions of packages wajig depends on: ii apt 0.6.46.4-0.1 Advanced front-end for dpkg ii dselect 1.13.25 user tool to manage Debian package ii python 2.4.4-6 An interactive high-level object-o ii python-apt 0.6.21 Python interface to libapt-pkg wajig recommends no packages. -- no debconf information -- William -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
