Description of problem:
The dund init script ends with error code 0 when the networking is not started
even though the service is not running. It also returns wrong error code of
uniplemented script feature (1 instead of 3).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. service network stop
2. service dund start/status
3. echo $?
correct error code/status of the service
When fixing this bug, please obbey our init script guidelines and be sure that
status command is run correctly.
Our guidelines are on following two pages:
For an example of the script that returns the error codes correctly and always
runs status see:
This bug is tracked by 237789.