Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bthidd(8) [freebsd man page]

BTHIDD(8)						    BSD System Manager's Manual 						 BTHIDD(8)

bthidd -- Bluetooth HID daemon SYNOPSIS
bthidd -h bthidd [-a BD_ADDR] [-c file] [-H file] [-p file] [-t val] DESCRIPTION
The bthidd daemon handles remote Bluetooth HID devices. The options are as follows: -a BD_ADDR Specify the local address to listen on. By default, the server will listen on ANY address. The address can be specified as BD_ADDR or name. If a name was specified, the bthidd daemon will attempt to resolve the name via bt_gethostbyname(3). -c file Specify path to the configuration file. The default path is /etc/bluetooth/bthidd.conf. -d Do not detach from the controlling terminal, i.e., run in foreground. -H file Specify path to the known HIDs file. The default path is /var/db/bthidd.hids. -h Display usage message and exit. -p file Specify path to the PID file. The default path is /var/run/ -t val Specify client rescan interval in seconds. The bthidd daemon will periodically scan for newly configured Bluetooth HID devices or disconnected ``passive'' Bluetooth HID devices and will attempt to establish an outgoing connection. The default rescan interval is 10 seconds. KNOWN LIMITATIONS
The bthidd daemon currently does not handle key auto repeat and double click mouse events. Those events work under X(7) just fine, but not in text console. This manual page needs more work. A manual page documenting the format of the /etc/bluetooth/bthidd.conf configuration file is needed as well. FILES
/etc/bluetooth/bthidd.conf /var/db/bthidd.hids /var/run/ SEE ALSO
kbdmux(4), vkbd(4), bthidcontrol(8) AUTHORS
Maksim Yevmenkin <> CAVEATS
Any Bluetooth HID device that has HUP_KEYBOARD or HUP_CONSUMER entries in its descriptor is considered as ``keyboard''. For each ``keyboard'' Bluetooth HID device, the bthidd daemon will use a separate instance of the virtual keyboard interface vkbd(4). Therefore the kbdmux(4) driver must be used to properly multiplex input from multiple keyboards. BSD
September 7, 2006 BSD

Check Out this Related Man Page

BTHCID(8)						    BSD System Manager's Manual 						 BTHCID(8)

bthcid -- Bluetooth Link Key/PIN Code Manager SYNOPSIS
bthcid [-fn] [-d device] [-m mode] [-s socket_name] bthcid [-h] DESCRIPTION
The bthcid daemon handles Link Key and PIN code requests for Bluetooth devices. It opens a raw HCI socket and listens for the following HCI events. Link_Key_Request bthcid scans the /var/db/bthcid.keys file for a cached link key matching the remote device BD_ADDR and, if found, the Link_Key_Request_Reply will be sent back to the device, otherwise the Link_Key_Request_Negative_Reply will be sent. Link_Key_Notification When a new link key is created by the device, it will be cached for future use in the /var/db/bthcid.keys link keys file, which will be created if it does not already exist. PIN_Code_Request The bthcid daemon checks its PIN cache for a matching remote device entry. If no PIN is found, the bthcid daemon will send a message to any PIN clients that have registered, with the device details and a timeout value. When no clients are available or the timeout has expired, bthcid will send a PIN_Code_Request_Negative_Reply back to the device. When a PIN is found, or if a client responds within the timeout period, a PIN_Code_Request_Reply will be sent back to the device. PINs received from clients will be cached for 5 minutes until used, and may be added to the cache prior to pairing with the btpin(1) utility. Some of the functionality of bthcid can be handled by the Bluetooth controller directly, and cached Link Keys may be examined, deleted or moved to device storage using the btkey(1) program. The command line options are as follows: -d device Specify the local Bluetooth device address. The default is BDADDR_ANY. -f Run in foreground (do not detach). -h Display usage message and exit. -m Specify the file mode access bits for the PIN client socket. The default is to allow readwrite access to user and group (0660). -n Do not listen for PIN clients. -s socket_name Specify the socket name to listen on for PIN clients. The default path is /var/run/bthcid. FILES
/var/db/bthcid.keys /var/run/bthcid /var/run/ SEE ALSO
btkey(1), btpin(1), bluetooth(4), btconfig(8) HISTORY
The bthcid daemon first appeared in FreeBSD 5.3 as hcsecd. It was ported to NetBSD 4.0 with its present name and extended to support PIN clients by Iain Hibbert under the sponsorship of Itronix, Inc. AUTHORS
Maksim Yevmenkin <> Iain Hibbert BSD
September 29, 2006 BSD
Man Page

Featured Tech Videos