Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

anyremote(1) [debian man page]

anyRemote(1)						      General Commands Manual						      anyRemote(1)

NAME
anyremote - control PC with Bluetooth/Wi-Fi cell phone .br SYNOPSIS
anyremote [-f file] [-s connect string] [-log] [-a] [-fe port] [-http] [-u username] [-name SDP service name] [-password] anyremote -h|-v .br DESCRIPTION
The overall goal of this project is to provide remote control service on Linux through Bluetooth, Wi-Fi or just TCP/IP connection. anyRemote supports wide range of modern cell phones like Nokia, HTC, SonyEricsson, Motorola and others. It was developed as thin "communication" layer between Bluetooth (IR, Wi-Fi)-capabled phone and Linux, and in theory could be configured to manage almost any software. anyRemote is console application, but in addition there are GUI front-ends for Gnome and KDE. OPTIONS
-h print short help and exit -v print version number and exit -f /path/to/configuration/file By default anyremote will try to find and use $HOME/.anyremote.cfg, then ./.anyremote.cfg. It is possible to specify configuration file directly with -f option. -s connect string where connect string can be one of: bluetooth:_channel_ (Server mode - bluetooth connection) socket:_port_ (Server mode - TCP/IP connection) web:_port_ (Server mode - Web interface) local:/dev/ircommX (Server mode - IR connection) rfcomm:XX:XX:XX:XX:XX:XX:CC (AT mode - bluetooth connection, where XX:XX:XX:XX:XX:XX is bluetooth device address and CC is channel number - integer from 1 to 32) /dev/ttyACM# (AT mode - cable connection) /dev/ircomm# (AT mode - IR connection) ilirc:_AF_LOCAL socket file_ (use with inputlircd) stdin -log print verbose logging information to $HOME/.anyRemote/anyremote.log -a reconnect automatically in case of connection failure, used only in AT-mode -fe _port_ Work as backend for GUI frontend. Use specified port to connect to frontend. -name SDP_service_name if bluetooth connection is used, allows one to specify SDP service name. Default value for SDP service name is "anyRemote" -password If this option is specified, then anyRemote will ask the client for the password. Password phrase should be stored in $HOME/.anyRemote/password file in plain text. -u|--user _username_ if started from root, allows one to set effective user ID to specified user .br AUTHORS
Mikhail Fedotov anyremote@mail.ru http://anyremote.sf.net .br BUGS
If you find any bugs, please report to anyremote@mail.ru .br LICENCE
This is free software. You may redistribute copies of it under the terms of the GNU General Public License http://www.gnu.org/licenses/gpl.html. There is NO WARRANTY, to the extent permitted by law. May 11, 2012 anyRemote(1)

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
Man Page