Your message dated Fri, 24 Mar 2006 11:29:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line obsolote bug
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: restartd
Version: 0.1.a-3
Severity: normal
Hi,
restartd default config file monitors bind:
bind ".*named" "/etc/init.d/bind restart" ""
This behaviour is undesirable on the majority of systems where bind is
not installed.
Furthermore it only works for bind8. On my system that runs bind9
named processes are displayed like this by ps:
bind 821 0.0 0.5 10992 2816 ? S Apr07 0:00 [named]
bind 823 0.0 0.5 10992 2816 ? S Apr07 0:00 [named]
bind 824 0.0 0.5 10992 2816 ? S Apr07 0:00 [named]
bind 825 0.0 0.5 10992 2816 ? S Apr07 0:00 [named]
bind 826 0.0 0.5 10992 2816 ? S Apr07 0:00 [named]
restartd detects that named does not run and tries to restart it
continuously. Moreover /etc/init.d/bind does not exist
(/etc/init.d/bind9 does) which causes error messages on the console.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux jophur.dyndns.org 2.4.20-1-686 #1 Sat Mar 22 13:16:21 EST 2003
i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
Versions of packages restartd depends on:
ii libc6 2.3.1-16 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
The latest version does not have bind, in particular nothing in the
configuration file.
Thus this bug should be closed.
Cheers,
Laszlo/GCS
--- End Message ---
