This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 522093 - init script has no status/restart/condrestart functions available
init script has no status/restart/condrestart functions available
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
:
Depends On:
Blocks: InitScriptsProject
  Show dependency treegraph
 
Reported: 2009-09-09 09:20 EDT by Vladimir Benes
Modified: 2009-09-16 07:13 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-09-16 07:13:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Vladimir Benes 2009-09-09 09:20:43 EDT
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:
Comment 1 Bastien Nocera 2009-09-09 09:56:05 EDT
What did you expect it to do when status/restart or condrestart was used?

The initscript just runs a single command and exits...
Comment 2 Vladimir Benes 2009-09-11 04:59:51 EDT
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
Comment 3 Bastien Nocera 2009-09-16 07:13:52 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.