Bug 1044674

Summary:	bluez-compat should use systemd
Product:	Red Hat Enterprise Linux 7	Reporter:	jcpunk
Component:	bluez	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	csieh, misterbonnie
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-07 08:37:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description jcpunk 2013-12-18 19:35:02 UTC

Description of problem: bluez-compat includes

/etc/rc.d/init.d/dund
/etc/rc.d/init.d/pand
/etc/rc.d/init.d/rfcomm

which could be converted to systemd services

Version-Release number of selected component (if applicable):bluez-compat-4.101-9.el7.x86_64.rpm


How reproducible: 100%


Steps to Reproduce:
1. install bluez-compat-4.101-9.el7.x86_64.rpm
2. look for systemd services
3. find legacy init scripts

Actual results:
legacy init scripts

Expected results:
systemd units

Additional info:

Comment 2 Bastien Nocera 2014-01-07 08:17:43 UTC

These initscripts are for obsolete commands that some users requested. They were removed in more recent versions of Fedora and bluez, and it's a great shame that we didn't make the switch to BlueZ 5.x before RHEL7, but I don't think that porting those obsolete initscripts to systemd, with all the testing and configuration file changes that it entails.

At best, I'd drop the -compat sub-package completely.

Comment 3 RHEL Program Management 2014-01-07 08:37:01 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.