Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Resources

Installation

$ sudo apt install ethtool

Configuration

  • Both: Ensure both primary (server) and secondary (client) pc's are aware of each other's hostnames (use /etc/hosts if there is no DNS server) 

  • Server: Create a configuration file (/etc/synergy.conf, ~/.synergy.conf are likely places)

  • Client: The client side needs no configuration except to be aware of the server's hostname.

Configuration File (Server PC)
# snorriheim is the server (also recorded in /etc/hosts on the clients)
# snorri-oryx is a client (recorded in /etc/hosts on the server)
# lenevo is another client (recorded in /etc/hosts on the server)

section: screens
  lenevo:
  snorriheim:
  snorri-oryx:
end

# Alisases seem to be oft needed when the hostname is other than
# the alias being used here
section: aliases
  lenevo:
    91106-DStonier.internal.tri.global
end

section: links
  lenevo:
    right = snorriheim
  snorri-oryx:
    left = snorriheim
  snorriheim:
    left = lenevo
    right = snorri-oryx
end

Execution

Execute Server and Client
# Server
synergys --config /etc/synergy.conf

# Clients
synergyc snorriheim

Debugging

Execute Server and Client
# Primary PC
synergys --debug DEBUG --no-daemon --config /etc/synergy.conf

# Secondary PC
synergyc --debug DEBUG snorriheim

Automation

Create some auto-start scripts and register these in the Autostart section of System Settings as a Script File, run on Startup.

The client side is happy running clients in parallel. I haven't tested parallelising on the server, but that too is probably fine (or there is a smarter way to do so in the configuration?).

/usr/local/bin/synergys-snorriheim (Server PC)
#!/bin/bash

synergys --config /etc/synergy.conf
/usr/local/bin/synergyc-snorriheim (Client PC)
#!/bin/bash

synergyc --debug DEBUG snorriheim
  • No labels