.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SYNERGYC" "1" "June 2, 2013" "" ""

.SH NAME
synergyc \- synergy client
.SH SYNOPSIS

\fBsynergyc\fR [ \fB--crypto-pass \fIpassword\fB\fR ] [ \fB-d \fIlevel\fB\fR | \fB--debug \fIlevel\fB\fR ] [ \fB--display \fIdisplay\fB\fR ] [ \fB--daemon\fR | \fB{ --no-daemon | -f }\fR ] [ \fB-l \fIlog-file\fB\fR | \fB--log \fIlog-file\fB\fR ] [ \fB-n \fIname\fB\fR | \fB--name \fIname\fB\fR ] [ \fB--no-tray\fR ] [ \fB--no-xinitthreads\fR ] [ \fB--restart\fR | \fB{ --no-restart | -1 }\fR ] [ \fB--yscroll \fIdelta\fB\fR ] \fB\fIaddress\fB\fR


\fBsynergyc\fR \fB { --help | -h }\fR


\fBsynergyc\fR \fB --version\fR

.SH "DESCRIPTION"
.PP
Starts the \fBsynergyc\fR mouse/keyboard 
sharing client.
.PP
This manual page was written for the Debian distribution
because the original program does not have a manual page.
.SH "OPTIONS"
.TP
\fB--crypto-pass \fIpassword\fB \fR
use \fIpassword\fR as the password for
authenticating to the synergy server.
.TP
\fB-d \fIlevel\fB --debug \fIlevel\fB \fR
use debugging level \fIlevel\fR\&.

Debug levels are from highest to lowest:  FATAL,
ERROR, WARNING, NOTE, INFO, DEBUG, DEBUG1, and DEBUG2.
Only messages at or above the given level are logged.
Messages are logged to a terminal window when running in
the foreground, and to syslog when running as a daemon.
.TP
\fB--display \fIdisplay\fB \fR
connect to the X server at \fIdisplay\fR
.TP
\fB--daemon \fR
run the client as a daemon.
.TP
\fB-f --no-daemon \fR
run in client the foreground.
.TP
\fB-l \fIlog-file\fB --log \fIlog-file\fB \fR
write log messages to \fIlog-file\fR
.TP
\fB-n \fIscreen-name\fB --name \fIscreen-name\fB \fR
use \fIscreen-name\fR instead of
the hostname.

This option lets the client use a name other than its
hostname for its screen. This name is used when checking
the configuration.
.TP
\fB--no-tray\fR
disable the system tray icon.
.TP
\fB--no-xinitthreads\fR
disable Xlib threading support.

This option may fix some crashing issues with Synergy.
.TP
\fB--restart \fR
restart the client automatically if it fails.
.TP
\fB-1 --no-restart \fR
do not try to restart the client if it fails for some
reason.
.TP
\fB          --yscroll \fIdelta\fB \fR
set the vertical scrolling delta to
\fIdelta\fR\&.  If this option is not
given, the default vertical scrolling delta is 120.
.TP
\fB-h --help \fR
display help and exit.
.TP
\fB--version \fR
display version information and exit.
.TP
\fB\fIaddress\fB \fR
address of server.

\fIaddress\fR has one of the
following forms:
.RS
.TP 0.2i
\(bu
\fIhostname\fR
.TP 0.2i
\(bu
\fIhostname\fR:\fIport\fR
.RE

\fIhostname\fR is a hostname or
address of a network interface on the server
system. \fIport\fR is a port number
from 1 to 65535.  \fIport\fR defaults
to 24800.
.SH "RUNNING THE CLIENT"
.PP
Run the client on all computers that aren't the server using
the following command line:

\fBsynergyc \fR \fB-f\fR \fB\fIserver-hostname\fB\fR

Replace \fIserver-hostname\fR with the
hostname or address of the server system. The `-f' option causes
synergy to run in the foreground. This option is recommended until
you've verified that the configuration works.
If you didn't include the system's
hostname in the configuration file (either as a screen name or
an alias) then you'll have to add `--name
\fIscreen-name\fR\&' to the command line,
where \fIscreen-name\fR is a name in the
configuration file.
.PP
The client should quickly report `connected to server'.  If it
does not but doesn't print an error and exit immediately then
it's trying to connect to the server but cannot.  It will time
out in 30 seconds and exit (use ctrl+c to exit earlier).  You
should check that the server is running and is reachable over
the network and try again.
.PP
If the client fails and exits it should print an error describing
the problem.  Here are typical problems and possible solutions:
.TP 0.2i
\(bu
failed to open screen:

check permission to open the X display

check that the DISPLAY environment variable is set
.TP 0.2i
\(bu
already connected:

check that the synergy client isn't already running
.TP 0.2i
\(bu
refused client:

add client to the server's configuration file
.TP 0.2i
\(bu
connection failed:

check \fIserver-hostname\fR

the server cannot open the desired port, stop the
program using that port (24800) and restart the
server
.PP
Once all the clients are running, try moving the mouse to each
screen.  Be sure to check all the configured links. 
.SH "STARTING AUTOMATICALLY"
.PP
Synergy requires an X server.  That means a server must be
running and synergy must be authorized to connect to that server.
I recommend to start the synergy client from a start script
of your desktop environment or window manager. The commands
should look something like this:

\fBpkill synergyc\fR


\fBsynergyc\fR [ \fB\fIoptions\fB\fR ] \fB\fIserver-hostname\fB\fR

.PP
If you are using GNOME, you can add the synergy client to the
list of the non-session-managed startup programs. For doing this,
start the control center, choose `Session Properties & Startup'
and then `Startup Programs'. Add a new entry with `\fB/usr/bin/synergyc
\fIserver-hostname\fB\fR\&' as the startup command.
.PP
\fIoptions\fR must not include `-f' or `--no-daemon'.
It's important to make sure no old copies of synergy are running so they
can't interfere with the new one.
.SH "BUGS"
.PP
The \fB--crypto-pass\fR option uses new cryptography
code that is not well-tested, and has been known to contain
security flaws.  See the synergys(1) man page, under NETWORK
SECURITY and BUGS, for a discussion of the security provided and
potential alternatives.
.SH "SEE ALSO"
.PP
synergys(1)
.SH "AUTHOR"
.PP
This manual page was written by Daniel Lutz <danlutz@debian.org> for
the Debian system. Edited by Titus Barik <barik@ieee.org>
and Jeff Licquia <licquia@debian.org>\&.