+++ This bug was initially created as a clone of Bug #237800 +++ Description of problem: Following code ends up with error code 0 when networking is not presented even though the service is not started. It also forbids the correct run of status command of the script. [ ${NETWORKING} = "no" ] && exit 0 AVAHI_BIN=/usr/sbin/avahi-daemon test -x $AVAHI_BIN || exit 5 It appears in both avahi-daemon and avahi-dnsconfd. Also incorrect return codes through the code are present. Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. service netowrk stop 2. service avahi-daemon start/status 3. echo $? Actual results: 0 Expected results: non-zero result with respect to our guidelines. Additional info: 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: http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html http://intranet.corp.redhat.com/ic/intranet/InitscriptGuidelines.html For an example of the script that returns the error codes correctly and always runs status see: http://devserv.devel.redhat.com/~mmarcini/amd This bug is tracked by 237789.
Created attachment 155008 [details] A proposed patch for the avahi-daemon init script
Created attachment 155009 [details] A proposed patch for the avahi-dnsconf init script
*** This bug has been marked as a duplicate of 246875 ***