Linux and UNIX Man Pages

Test Your Knowledge in Computers #167
Difficulty: Easy
The Transmission Control Protocol (TCP) is one of the least used protocols of the Internet protocol suite.
True or False?
Linux & Unix Commands - Search Man Pages

bthidd(8) [freebsd man page]

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

NAME
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/bthidd.pid. -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/bthidd.pid SEE ALSO
kbdmux(4), vkbd(4), bthidcontrol(8) AUTHORS
Maksim Yevmenkin <m_evmenkin@yahoo.com> 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

BTHIDEV(4)						   BSD Kernel Interfaces Manual 						BTHIDEV(4)

NAME
bthidev -- Bluetooth Human Interface Device support SYNOPSIS
bthidev* at bthub? btkbd* at bthidev? reportid ? btms* at bthidev? reportid ? DESCRIPTION
The bthidev driver handles all Bluetooth Human Interface Devices. Each HID device can have several components, e.g., a keyboard and a mouse. These components use different report identifiers to distinguish which component data is coming from. The bthidev driver may have several children attached that handle particular components and dispatches data to them based on the report id. Normally, Bluetooth HIDs will be attached using the btdevctl(8) program. The following properties are used by the bthidev driver during autoconfiguration: local-bdaddr Local device address. remote-bdaddr Remote device address. service-name The bthidev driver matches the 'HID' service. control-psm This, if set, will indicate the PSM to use for the Control channel. If not set, L2CAP_PSM_HID_CNTL will be used. interrupt-psm This, if set, will indicate the PSM to use for the Interrupt channel. If not set, L2CAP_PSM_HID_INTR will be used. descriptor This required binary blob is the HID descriptor containing information about reports the device will produce, and obtained via SDP. reconnect If this boolean value is set, and is true, then the bthidev driver will initiate reconnections to the remote device when no connection is present. link-mode This optional string represents the link mode of the baseband link, and may be one of 'auth', 'encrypt', or 'secure'. When the bthidev driver has configured its children, it will initiate a connection to the remote device. If this fails and the reconnect flag is not set, it will then wait for the device to initiate the connection. SEE ALSO
bluetooth(4), bthub(4), btkbd(4), btms(4), btdevctl(8) HISTORY
The bthidev driver was written by Iain Hibbert under the sponsorship of Itronix, Inc. and first appeared in NetBSD 4.0. BSD
April 10, 2007 BSD

Featured Tech Videos