Bug 433647

Summary:	Malformed LSB init script headers
Product:	[Fedora] Fedora	Reporter:	Nils Philippsen <nphilipp>
Component:	bluez-utils	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	bnocera, jtane
Target Milestone:	---	Keywords:	EasyFix
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/initscrcomconv.html
Whiteboard:
Fixed In Version:	3.31-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-21 00:18:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nils Philippsen 2008-02-20 16:50:58 UTC

Description of problem:

The LSB-style comment headers are malformed in these init script files:
/etc/rc.d/init.d/bluetooth
/etc/rc.d/init.d/dund
/etc/rc.d/init.d/pand

To continue the description on the next line, the hash must be followed by two
spaces or one tab, see the LSB spec for more details:

http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/initscrcomconv.html

Version-Release number of selected component (if applicable):
bluez-utils-3.20-6.fc8

Additional info:

I'll utilize the description headers in a future version of
system-config-services and the description of these daemons only contains the
first line (because the line continuation doesn't work).

Comment 1 Bastien Nocera 2008-03-26 12:13:02 UTC

All the initscripts are available in CVS, without any special build. Would you
mind correcting them and providing a patch, as I'm not certain me fixing it
wouldn't have it break in another way.

Also, it would be useful if system-config-services, or chkconfig could provide
an application to spot this sort of errors.

Comment 2 Bastien Nocera 2008-04-02 14:21:03 UTC

*** Bug 440244 has been marked as a duplicate of this bug. ***