Red Hat Bugzilla – Bug 158722
bluetooth initscript should start erlier
Last modified: 2012-06-20 09:31:30 EDT
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):
Steps to Reproduce:
1. install bluez-utils
2. chkconfig bluetooth on
3. ls -l /etc/rc5.d/S*
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?
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.