changed notes about how to startup configure synergy. it now
discourages using boot scripts, which can't handle X servers requiring authorization, and suggests modifying xdm's Xsetup.
This commit is contained in:
parent
587f5247d8
commit
4c2cbb9f03
75
README
75
README
|
@ -226,29 +226,16 @@ linux, unix:
|
|||
before starting synergy as a daemon you should understand that
|
||||
synergy requires an X server that it can connect to. synergy
|
||||
can start before the X server does and will repeatly attempt to
|
||||
connect to the X server until it succeeds. the DISPLAY env var
|
||||
should be set appropriately before starting synergy. note that
|
||||
it probably will not be set when running startup scripts so you
|
||||
have to set it yourself (probably to ":0"). if it's not set
|
||||
then synergy will use the default ":0.0" which is correct in
|
||||
most cases.
|
||||
connect to the X server until it succeeds. however, if the
|
||||
server requires authorization then it's unlikely that synergy
|
||||
will ever succeed. in that case synergy should be (re)started
|
||||
by the X display manager.
|
||||
|
||||
if the X server goes down then all the clients connected to it
|
||||
must terminate. synergy has to deal with this because some
|
||||
display managers will automatically restart the X server when
|
||||
a user logs out. synergy can automatically restart itself and
|
||||
it does so by default. the `--no-restart' option turns this
|
||||
feature off.
|
||||
|
||||
some display managers also prevent any X client other than
|
||||
those they themselves start from connecting to the X server
|
||||
during login for security reasons. for these display managers,
|
||||
synergy should be part of the manager's screen initialization
|
||||
script and synergy should be started with the --no-restart
|
||||
option since the display manager will do the restarting.
|
||||
otherwise, synergy should not use the --no-restart option and
|
||||
it can be started at boot time (sometime after the network is
|
||||
started) or when the X server is started.
|
||||
the DISPLAY env var should be set appropriately before starting
|
||||
synergy. note that it probably will not be set when running
|
||||
boot scripts so you have to set it yourself (probably to ":0").
|
||||
if it's not set then synergy will use the default ":0.0" which
|
||||
is correct in most cases.
|
||||
|
||||
finally, some display managers (xdm and kdm, but not gdm)
|
||||
grab the keyboard and do not release it until the user logs
|
||||
|
@ -259,21 +246,40 @@ linux, unix:
|
|||
|
||||
to install synergy as a daemon, you'll need to add the
|
||||
appropriate lines and/or files to start synergy at boot time
|
||||
or as part of a display manager screen initialization script.
|
||||
or modify the display manager screen initialization scripts.
|
||||
do not use the `-f' or `--no-daemon' options. for the server
|
||||
use the `--config' option to specify the path to the
|
||||
configuration file or just put the configuration in
|
||||
/etc/synergy.conf.
|
||||
|
||||
linux:
|
||||
if starting synergy from xdm's or kdm's screen initialization
|
||||
script you'll want add a line to start synergy in
|
||||
/etc/X11/xdm/Xsetup_0, probably near the bottom. you'll also
|
||||
want to put the configuration file in /etc/synergy.conf and
|
||||
the synergy executable in /usr/sbin. to uninstall, remove the
|
||||
added line and files.
|
||||
you should modify xdm's Xsetup script to start the synergy
|
||||
client or server. for example, somewhere near the bottom of
|
||||
Xsetup (but someplace before anywhere the script calls exit)
|
||||
you might add:
|
||||
/usr/bin/killall synergy
|
||||
/usr/sbin/synergy 192.168.1.101
|
||||
this assumes synergy is installed in /usr/sbin. these lines
|
||||
make sure any already running synergy is terminated and starts
|
||||
a fresh copy. it's important to kill old copies so that you
|
||||
don't end up with multiple synergy instances fighting each
|
||||
other or, at the very least, using up system resources.
|
||||
|
||||
if starting the synergy client using init.d then:
|
||||
to start the synergy server you might use:
|
||||
/usr/bin/killall synergyd
|
||||
/usr/sbin/synergyd --config /root/synergy.conf
|
||||
assuming synergyd is installed in /usr/sbin. if you've put
|
||||
the configuration data in /etc/synergy.conf then you don't
|
||||
need the --config option.
|
||||
|
||||
another option is to put the synergy startup in .Xsession in
|
||||
your home directory. that allows users without root access to
|
||||
start synergy when they login. in this case synergy will not
|
||||
be running while on the login screen.
|
||||
|
||||
if your X server does not require authorization then you can
|
||||
start synergy at boot time. if starting the synergy client
|
||||
using init.d then:
|
||||
# /bin/cp synergy /usr/sbin/synergy
|
||||
# /bin/cp synergy.linux.init /etc/init.d/synergy
|
||||
# /sbin/chkconfig --add synergy
|
||||
|
@ -305,7 +311,11 @@ linux:
|
|||
# /bin/rm /etc/synergy.conf
|
||||
# /bin/rm /etc/init.d/synergyd
|
||||
# /bin/rm /usr/sbin/synergyd
|
||||
|
||||
|
||||
note that synergy.linux.init and synergyd.linux.init are not
|
||||
tested on a wide variety of platforms and may need editing
|
||||
for your platform.
|
||||
|
||||
|
||||
common command line options
|
||||
---------------------------
|
||||
|
@ -455,4 +465,5 @@ tips and tricks
|
|||
* turn off mouse driven virtual desktop switching on X windows. it
|
||||
will interfere with synergy. use keyboard shortcuts instead.
|
||||
|
||||
* synergy's screensaver synchronization works best with xscreensaver.
|
||||
* synergy's screensaver synchronization works best with xscreensaver
|
||||
under X windows.
|
||||
|
|
Loading…
Reference in New Issue