Bug 158722

Summary: bluetooth initscript should start erlier
Product: Red Hat Enterprise Linux 4 Reporter: Hans-Gerd van Schelve <van-schelve>
Component: bluez-utilsAssignee: Ric Wheeler <rwheeler>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 4.0CC: mherbert
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 13:31:30 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 Hans-Gerd van Schelve 2005-05-25 08:01:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
During init the bluetooth start script ist calling at step S25bluetooth. We are using bluetooth phones for our netwrok connection so we need start of bluetooth erlier than network. Our suggestion is to start bluetooth on position S07bluetooth. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. install bluez-utils
2. chkconfig bluetooth on
3. ls -l /etc/rc5.d/S*

Additional info:

Comment 1 David Woodhouse 2006-09-10 08:39:19 UTC
Unfortunately we're also constrained by the use of dbus -- we have to start
bluetooth after dbus is running.

What's the failure mode? You're using dialup over rfcomm? Doesn't the ppp just
keep failing until the /dev/rfcommX device exists, and then manage to start
correctly after that?

Comment 3 Jiri Pallich 2012-06-20 13:31:30 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.