FS#10445 - bluez: dund starts before sdp service finish initialization
Attached to Project:
Arch Linux
Opened by Sergej Pupykin (sergej) - Sunday, 18 May 2008, 21:25 GMT
Last edited by Jan de Groot (JGC) - Saturday, 02 May 2009, 15:28 GMT
Opened by Sergej Pupykin (sergej) - Sunday, 18 May 2008, 21:25 GMT
Last edited by Jan de Groot (JGC) - Saturday, 02 May 2009, 15:28 GMT
|
Details
Description:
dund starts before sdp service finish initialization. >> May 19 01:15:32 home dund[6745]: Failed to connect to the local SDP server. Connection refused(111) appears in everything.log Additional info: bluez-libs 3.31-1 bluez-utils 3.31-1 Steps to reproduce: Start bluetooth with hcid and dund. This problem can be resolved by adding 'sleep 1' into /etc/rc.d/bluetooth between hcid and dund start. |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 02 May 2009, 15:28 GMT
Reason for closing: Fixed
Additional comments about closing: Added a sleep 1 for now. Launching netstat in a loop doesn't look like the correct solution to me.
This daemon has braindead initialization code, it forks before initializing and doesn't cleanup the socket when it's killed.
Saturday, 02 May 2009, 15:28 GMT
Reason for closing: Fixed
Additional comments about closing: Added a sleep 1 for now. Launching netstat in a loop doesn't look like the correct solution to me.
This daemon has braindead initialization code, it forks before initializing and doesn't cleanup the socket when it's killed.
while [ `netstat -xln| grep /var/run/sdp | wc -l` -eq 0 ]; do
sleep 1;
done
When sdp started, /var/run/sdp socket appears in netstat -xln output.