Your message dated Sun, 4 Nov 2007 14:28:41 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426969: wajig: control of /etc/init.d/ script
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Received Fri 01 Jun 2007 2:44pm +1000 from William Xu:
> 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.
Thanks for the bug report William. This has been fixed, using
/etc/init.d/... rather than invoke-rc.d ...
Will be released shortly in version 2.0.38
Regards,
Graham
--- End Message ---
