- Ubuntu Documentation
- Quickstart Guide
- On the Server
- Using Synergy GUI
- Using QuickSynergy
- On the Client(s)
- Using Synergy GUI
- Using QuickSynergy
- Manual Configuration
- On the Server
- Running Synergy
- Autostart Synergy after logging in (GNOME)
- On the Server
- On the Client
- Autostart Synergy before logging in (GDM)
- On the Server
- On the Client
- Autostart Synergy before logging in (KDM)
- On the Client
- Autostart Synergy before logging in (LightDM)
- On the client
- On the server
- See Also
- Synergy
- How does Synergy Workshop work?
- What type of content is supported?
- How do I upload something to Synergy Workshop?
- Why are dedicated servers not supported right now.
- When is the next Rebel Rush event?
Ubuntu Documentation
Needs Updating
This article needs updating to include the latest versions of Ubuntu. More info.
Synergy is a program that will let you use one keyboard and mouse on multiple computers across a network. The computers can be running Linux, Windows, or OS X. The computer with the keyboard and mouse is the server or host, and the computers with the displays to be controlled remotely are the clients. This HOWTO lets you know how to get Synergy set up and running on your Ubuntu system.
Warning! Synergy is not very secure at all! Consider — you are setting up something to allow an entirely different computer control the keyboard and mouse on your own computer! Don’t try and use this anywhere unsecure! There is a way of making it more secure by running it over OpenSSH, but that is currently beyond the scope of this article. More documentation is available on the Synergy website.
NOTE: The more current release versions of Synergy include the server, client, and a GUI in one package. Additionally, the newer versions have added encryption. Most of this guide is dated if you are using the newer versions from the Synergy website mentioned above.
Quickstart Guide
There are three ways of using Synergy. The first two are provided by the synergy package, while the third is provided by a third-party application called QuickSynergy.
If you choose to use only the first-party methods, you can install synergy from the software center or their website.
On the Server
Follow one of these section steps on the computer with the keyboard and mouse. If you don’t know the hostname of the server, run the hostname command from a Terminal window.
Using Synergy GUI
Install Synergy and open it
Using QuickSynergy
Install QuickSynergy and open it (under Applications > Accessories)
On the Client(s)
Follow these steps on the computer you would like to control with a remote keyboard and mouse.
Using Synergy GUI
Install Synergy and open it
Select the ‘client’ option
In the main window, type the IP address of the Host machine in the IP field, or use the hostname found above with .local added to the end
Using QuickSynergy
Install QuickSynergy and open it (under Applications > Accessories)
Under the ‘Use’ tab, type the IP address of the Host machine in the IP field, or use the hostname found above with .local added to the end. Type in the hostname of the Client machine in the Screen field.
Manual Configuration
The following steps assume you are setting up synergy on a host computer named myserver and a client computer named myclient.
On the Server
Synergy configuration can go in your home folder called .synergy.conf or in /etc/synergy.conf. It is up to you whether you would like the changes to be per-user or system-wide.
Here is a sample configuration that will be the needs of 95% of users:
myserver is the hostname of the computer running synergys (providing the keyboard and mouse) myclient is the hostname of the computer running synergyc (using the keyboard and mouse provided by myserver) section: screens is where you set the host names of the computers going to be used. section: links is what side the mouse will leave the screen of one computer to reach the desktop of the other. myserver is set to the left of myclient, so when I drag the mouse off the right hand side of myserver‘s screen it appears on the left hand side myclient‘s screen. Use up/down instead of left/right to establish and over/under sort of relationship.
Running Synergy
From the server, run the command:
From the client, run the command:
Replacing with either the hostname (myserver) or IP address of myserver.
You should now be able to move your mouse pointer off the right edge of your server’s screen and see it show up at the left side of your client’s screen. See the steps in the next section to make synergy start automatically on the host and client computers.
If you have any problems at this point it is helpful to run synergys and synergyc in the foreground with the -f option. This allows you to see error/status information that synergy prints to the terminal.
Autostart Synergy after logging in (GNOME)
On the Server
Follow these steps to start synergys when you log into GNOME.
Go to System Menu > Preferences > Startup Applications. Click «Add» and enter
If you want to use the configuration set up with QuickSynergy use this instead:
Click OK and Close.
On the Client
Follow these steps to start synergyc when you log into GNOME.
Go to System Menu > Preferences > Startup Applications. Click «Add» and enter
Replacing with either the hostname or IP address of myserver.
Click OK and Close.
Autostart Synergy before logging in (GDM)
Note: Autostarting Synergy before logging in requires that your network connection be available at all times and not just after you log in. This is accomplished by enabling the network connection for all users. To do this, choose System->Preference->Network Connections. Choose the network name and select Edit. Select «Available to all users», and then click «Apply». This connection will now be available at all times, including at the GDM login screen.
To make sure synergy is running at all times, the following has to happen: First, synergy is started when the GDM login screen starts. Then, synergy is killed and restarted when a user logs in. When the user logs out, synergy is killed and GDM starts it again. To edit system configuration files in the following sections open a text editor as the root user:
On the Server
At the end of the file /etc/gdm/Init/Default, just before the line that says exit 0 add the following:
Add the following to the end of /etc/gdm/PostLogin/Default (create this file file if it does not already exist):
If you created the file, make sure it is executable with this command:
Now, create a session file /etc/X11/Xsession.d/85synergys with the following contents
Lastly, we must make the file executable with this command:
On the Client
At the end of /etc/gdm/Init/Default, just before the line that says exit 0 add the following:
Be sure to replace with the host name or IP address of the computer running synergys.
NOTE: If your system has been configured to login automatically, this step may cause ubuntu to hang right before going to the desktop. If this is the case, remove these lines from /etc/gdm/Init/Default and everything should work properly. If your system is hanging at this stage, you can hit CTRL-ALT-F1 to login through command line and edit this file.(Tested on 10.04LTS Lucid Lynx)
Add the following to the end of /etc/gdm/PostLogin/Default (create this file file if it does not already exist):
If you created the file, make sure it is executable with this command:
Now, create a session file /etc/X11/Xsession.d/85synergyc with the following contents
This will run synergyc when any user logs in. Be sure to replace with the host name or IP address of the computer running synergys. Lastly, we must make the file executable with this command:
Autostart Synergy before logging in (KDM)
On the Client
Follow these steps to start the synergyc client when the KDM login screen launches.
Add the following to the end of /etc/kde3/kdm/Xsetup:
Be sure to replace with the host name or IP address of the computer running synergys.
For the client file we must also edit the Xstartup script to kill our synergyc process running as root before the user Xsession scripts run. To do this add the following to the end of /etc/kde3/kdm/Xstartup and it should look like this:
Autostart Synergy before logging in (LightDM)
On the client
Add the following line at the end of /etc/lightdm/lightdm.conf:
Where is the name/IP of the server you are connecting to.
On the server
Add the following line at the end of /etc/lightdm/lightdm.conf:
Where is the path to your config file for synergy (see above for typical locations).
On the Ubuntu 14.04 64bit the configuration file changed to /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf, and you need add this line at the end of the file:
On the Ubuntu 14.10 64bit add the line above to /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf.
See Also
SynergyHowto (последним исправлял пользователь ckimes 2017-09-16 20:32:50)
The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details
Источник
Synergy
Not many updates this week. There isn’t a current
changelog for the new 56.13 of synergy.
There have been some new added features which are still a Work in progress.
For instance the shell casings update not many have noticed yet but if you shoot the smg1 or shotgun you will see that actual physics shell casings come out and hit the floor just as a normal shell casing should. They can be stepped on and moved around (client side)
Also donators have a new addition to their playermodel selection
Comments
Just a heads up. We’ll try our best to keep you guys updated as much as possible.
Our coder has thrown a few updates in the past week that fixes a few issues (no changelog for that),
As you know we barely post news and updates on what’s going on. We’ll try to keep our changes in order.
Rebel rush event is not yet scheduled. I will keep you posted.
Every week I or another team member will be posting some updates/changelogs.
Just to keep you guys in the «know».
Thank you so much for being a part of Synergy till this very day.
We hope to release some crazy new things very soon.
Heya folks, here is another update for ya with various internal improvements.
If you find any issues with this update, please post the details in the forums and I’ll be sure to check it out.
Please note that if you have a Workshop Add-on (not «Item Replacements») currently active in the Synergy Workshop you need to re-update it. This update removed the VPK requirement for Add-ons to solve various engine issues. All you need to do is select your Add-on in the Workshop Publisher Menu and do an «Update Item» and re-upload your content. Workshop standards are now out of beta so these requirements will no longer change.
Also a Rebel Rush event will be coming up soon so stay tuned!
- Synergy will now automatically mount and manage all content.
- Users no longer need to manage their game mounts.
- Content will be automatically mounted and unmounted as needed.
- Removed the need for mount.cache, SteamContent.manifest, basemaps.txt, LevelContent.manifest files and the GameList menu.
- Further decreased average load times.
- Include files (.inc) are no longer required and will not exit Synergy with an error, but are still needed to tell Synergy which content a map needs to mount. Maps without a corresponding include file will default to Half-Life 2 content only.
- Maps that are a part of a specific game (i.e. a content file: content/*.dat) no longer require Include files.
- Added support for the following languages (Interface, Voiceovers, and Closed Captions) — Synergy will now choose the correct language pack based on Steam or in-game settings (Special thanks to user Allower for pointing this out with his Workshop fix):
- French
- German
- Italian
- Korean
- Spanish
- Russian
- Simplified Chinese
- Traditional Chinese
- Danish (UI Only)
- Dutch (UI Only)
- Portuguese (UI Only)
- Removed unnecessary Half-Life 2: Episode One requirement for Episode Two.
- Fixed all known cases of the «Closing pack file with -1 open files!» error.
- Added content files for the following games:
- Age of Chivalry
- Counter-Strike: Source
- Day of Defeat: Source
- Dystopia
- Eternal Silence
- Half-Life 2: Update
- NEOTOKYO
- Portal
- Team Fortress 2
- Zombie Panic: Source
- Workshop:
- Add-on (non-‘Item Replacement’) items will no longer be stored in VPKs. (Fixes various issues with BSPs being stored in VPKs)
- NOTICE: Existing Add-ons require a re-update in order to mount properly! (i.e. not packed in VPKs)
- Add-on items will mount all VPKs in it’s root directory.
- Added a «Workshop Settings» Menu to Prioritize Subscriptions.
- Added more helpful Messages during Workshop Item publishing.
- Add-on’s will now show in the Create a Server menu.
- Add-on (non-‘Item Replacement’) items will no longer be stored in VPKs. (Fixes various issues with BSPs being stored in VPKs)
- Fixed (and updated) donors not working due to a recent change in the SteamID format.
- Added support for loading a random background map on launch from the pool of what content you have available in the Advanced Multiplayer Options menu.
- Fixed a few cases of missing textures on a listen server.
- Fixed Synergy’s custom weapon sounds not playing. (Again)
- Properly removed cheat flag from stopsound command.
- Enabled sv_airaccelerate and sv_rollangle (camera sway) convars.
- Added conver glow_max to limit the maximum number of object outlines to render at once.
- Fixed a client crash on Linux.
- Replaced Convar toggle_show_players with hud_player_info_enable to toggle the Avatar over player’s heads.
- Added support for mounting content inside the «custom» folder (synergy/custom) to enable, set contentloader_custom_folder_enable to 1. This will also mount all VPKs found in the root of the folder.
Hey folks! Been quite some time! I hope over the next few months to have some time to give Synergy the attention it needs! This round we’re releasing Steam Workshop for Synergy. We know you like to mod Synergy up so we figured having a centralized and game-supported implementation is the way to go to keep it easy as possible.
How does Synergy Workshop work?
You do not have to restart Synergy in order to mount new Workshop items you’ve subscribed to; they will be automatically mounted the next time you load a level (if the item is finished downloading).
We have a few small test example items to toy with, but it may take some time for users add their own content.
What type of content is supported?
How do I upload something to Synergy Workshop?
Why are dedicated servers not supported right now.
The new method (known as ISteamUGC) is the next version of Workshop support for Steam games. The previous method used the Steam cloud which had many limitations. The new method supports unlimited file sizes and file counts and can be updated frequently and easily using the SteamPipe content system for fast and small downloads/updates.
So head on over! If you have suggestions to help improve Synergy Workshop or just wish to report a bug, please create a post in the new Workshop Discussion!
Other minor fixes in this update (55c):
- Fixed players not taking drown damage.
Changes in 55d (12-16-2014):
- Added player outlines that visually represent the player’s health when obstructed.
- Updated Donors.
- Fixed a few Workshop bugs.
- Added support for dynamic skies (See this Workshop Item for an example.)
When is the next Rebel Rush event?
Back so soon? Yep! We decided to go ahead and publish the ‘beta branch (2013)’ of Synergy to replace the previous 2007 version. What this means is Synergy will now play nice with Steampipe, and should work as expected from now on.
To ensure this process goes as smoothly, clean, and error free as possible, we recommend reinstalling Synergy via right clicking Synergy, “Delete Local Content”, then re-downloading. Synergy is now a SteamPipe app, meaning it resides within the steamapps\common directory now. Make sure Half-Life 2 and friends (episodes) are converted to this new format as well in order to play them within Synergy (which they should be if you played them recently).
This is our first ‘official’ release of this version, so there may be minor bugs present but this version should fix most if not all of the flakey issues over the last 6 months caused during the SteamPipe transition.
Thanks and stay tuned for Mac and Linux support!
Источник