Description of problem: SSIA Version-Release number of selected component (if applicable): bluez-4.52-1.fc12 How reproducible: 100% Steps to Reproduce: 1.run service bluetooth status/restart/condrestart 2. 3. Actual results: Usage: /etc/init.d/bluetooth {start|stop} Expected results: perform action as expected Additional info:
What did you expect it to do when status/restart or condrestart was used? The initscript just runs a single command and exits...
I am not sure but isn't system-config-services using status? Moreover this page (LSB init script compliance project) tells me that start/stop/restart/status/!force-reload! is mandatory see: https://wiki.test.redhat.com/BaseOs/Projects/InitScripts#Testtemplate
status, restart and condrestart would do absolutely nothing for this initscript that just pokes at udev on bootup. Furthermore, OS initscripts don't have to be LSB compliant, 3rd party initscripts should be, and the init system should support them. That initscript does not break LSB compliance.