anyremote --version (return code: 0)
anyremote v6.6.1
anyremote --help (return code: 0)
Usage: anyremote [-f conf.file] [-s peer[,peer ...]] [-log] [-a]
[-cfgdir directory] [-tmpdir directory]
[-fe port] [-u username] [-name SDP service name] [-password]
or: anyremote -h|-v
-h|--help print this help
-v|--version print version of anyRemote
-f /path/to/file specify configuration file
-s peer[,peer ...], where peer possible values are
tcp:<port> (Server mode - TCP/IP connection)
bluetooth:<channel 1-32> (Server mode - bluetooth connection)
web:<port> (Server mode - Web interface)
cmxml:<port> (Server mode - XML interface for Cisco IP phones)
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
avahi - register SDP service using Avahi
Default peer value is bluetooth,tcp:5197,web:5080,avahi
It is possible to specify several peers for Server mode configuration files only
It is possible to specify only single peer of web: or cmxml: type
-log print verbose logging information to $HOME/.anyRemote/anyremote.log
-cfgdir override default location of directory with configuration files
-tmpdir override default location of directory to store temporary files
-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 or TCP/IP connection is used, allows one to specify SDP service name
-password ask password on connect
password should be stored in $HOME/.anyRemote/password file in a plain text
-u|--user <username> if started from root, allows one to set effective user ID to specified user