[Bug 659785] New: bind: Init script "named" not fully LSB compliant
https://bugzilla.novell.com/show_bug.cgi?id=659785 https://bugzilla.novell.com/show_bug.cgi?id=659785#c0 Summary: bind: Init script "named" not fully LSB compliant Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: joschibrauchle@gmx.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729; .NET4.0C) Similar to the init script of the DHCPD (https://bugzilla.novell.com/show_bug.cgi?id=640336), the init script "named" of bind is not fully LSB compliant. When the configuration file of named is not found in the beginning of the init script, it returns exit code 6 (which is not valid if the "status" parameter was given), regardless of the real state of the daemon. The problem arises in a Heartbeat/Linux-HA configuration, where the Heartbeat service runs a ressource monitor using "rcnamed status" to check the status of this ressource. If the configuration file is not available at the time this command is run (e.g. when the configuration file is on an DRBD device which is not yet mounted), then the exit code of "6" will cause the Heartbeat monitor to fail, as this exit code is not expected from the "status" parameter! The solution to this problem should be similar if not identical to the above mentioned link to the DHCPD init script. Reproducible: Always Steps to Reproduce: 1. Link /etc/named.conf to a file on a DRBD device. 2. Unmount the DRBD device. 3. Check named status with "rcnamed status" Actual Results: Exit code 6 is returned, independent of the actual state of named. Expected Results: It should return the correct status of named (which will be most likely "not running", but may be different). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c
wei wang
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c1
Uwe Gansert
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c2
--- Comment #2 from Joschi Brauchle
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c3
--- Comment #3 from Joschi Brauchle
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c4
Uwe Gansert
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c5
Uwe Gansert
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c6
--- Comment #6 from Joschi Brauchle
https://bugzilla.novell.com/show_bug.cgi?id=659785
https://bugzilla.novell.com/show_bug.cgi?id=659785#c7
--- Comment #7 from Uwe Gansert
participants (1)
-
bugzilla_noreply@novell.com