After installation and configuring Bluetooth service, the command "sdptool browse local" has not given anything. I have written small additions to rc scripts, whether it is possible to include them in the given service? # diff /etc/conf.d/bluetooth /etc/conf.d/bluetooth.ORIG 12,14d11 < # Config file for sdpd < SDPD_CONFIG="/etc/bluetooth/sdpd.conf" < # diff /etc/init.d/bluetooth /etc/init.d/bluetooth.ORIG 48,55d47 < < ListService=`cat $SDPD_CONFIG | grep -v \# | grep ListService | sed s/ListService=\"// | sed s/\"//` < for i in $ListService < do < echo -n $i" " < /usr/bin/sdptool add $i > /dev/null < done < echo " " # cat /etc/bluetooth/sdpd.conf # Add to ListService # DID for Device ID Profile service # SP for Serial Port service # DUN for Dial-Up Networking service # LAN for LAN Access over PPP service # FAX for Fax service # OPUSH for OBEX Object Push service # FTP for OBEX File Transfer service # HS for Headset service # HF for Handsfree service # SAP for SIM Access service # NAP for NAP (Access to SIM) service # GN for Group Network service # PANU for PAN User service # HID for Human Interface Device service # CIP for Common ISDN Access # CTP for Cordless Telephony service # A2SRC for Audio source service # A2SNK for Audio sink service # SYNCML for SyncML Client service record ListService="DID SP DUN LAN FAX OPUSH FTP HS HF SAP NAP GN PANU HID CIP CTP A2SRC A2SNK SYNCML"
After installation and configuring Bluetooth service, the command "sdptool browse local" has not given anything. I have written small additions to rc scripts, whether it is possible to include them in the given service?
(In reply to comment #1) > After installation and configuring Bluetooth service, the command "sdptool > browse local" has not given anything. I have written small additions to rc > scripts, whether it is possible to include them in the given service? > Sorry about you not getting a response sooner but bluez has been pretty much unmaintained for months. Please attach a unified diff (diff -u) of any changes you would like to see and I will look at it.
master_volkov could you please give us an example why you need this? Usually the bluetooth daemons register the SDP records theirselves. For example hidd registeres HID and gnome-obex-server registers OPUSH.
With 3.10.1: betelgeuse@pena ~ $ sdptool browse local Browsing FF:FF:FF:00:00:00 ... Service Name: Obex Push Server Service Description: KDE OBEX Object Push Service Service RecHandle: 0x10000 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 3 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100 Service Name: KBtSerialChat Service Description: KDE Bluetooth Serial Chat Service Service RecHandle: 0x10001 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 Service Name: KDE Bemused Server Service Description: KDE Server for the Bemused remote control protocol Service RecHandle: 0x10002 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 27 The new services architecture takes care of this so the init script does not need to do it. Take a look at /etc/bluetooth/*.service in 3.10.1
