nodge’s blog

Start Registry Editor.

Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

On the Edit menu, click Modify, and then click Decimal.

Type the new port number, and then click OK.

Quit Registry Editor.

Installation¶

Docky ist nicht in offiziellen Quellen verfügbar, kann aber ab Ubuntu Karmic Koala 9.10 aus einem PPA bezogen werden.

Aus PPA-Quelle¶

Um das Programm aus dem PPA

ppa von docky-core zu installieren, muss, abhängig von der Ubuntu-Version, eine der folgenden Paketquellen eingetragen werden:

Hinweis!

Zusätzliche Fremdquellen können das System gefährden.

Für Ubuntu Karmic Koala 9.10:

ppa:docky-core/ppa (über Synaptic oder Softwareverwaltung KDE)

oder

deb http://ppa.launchpad.net/docky-core/ppa/ubuntu karmic main

Um die Quelle zu verwenden, sollte man den Signierungsschlüssel für diese Quelle einspielen. Dazu verwendet man folgenden Befehl:

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3528AE20  

Das zu installierende Paket ^[1] heißt:

• docky

Nach der Installation ist das Programm bei GNOME unter "Anwendungen -> Zubehör -> Docky" zu finden. Für eine korrekte Darstellung sollten Desktop Effekte aktiviert sein.

Scott Merrill writes in to say:

I noticed recently that ssh connections from my Ubuntu laptop to my
Debian server would time out and disconnect if I left the connection
idle for a long-ish period of time. This really annoyed me, because my
Debian desktop does not exhibit this behavior when connecting to the server.

I added the following line to /etc/ssh/ssh_config :
ServerAliveInterval 5

That seems to have fixed the problem, and my laptop can now remain
connected, though idle, to my server. Maybe this will help someone
else, too.

What this does, essentially is every 5 seconds, the client sends a small keep-alive packet to the server to make it look like the ssh connection is being actively used. The reason for Scott’s timeout could be a NAT firewall that seeks to minimize the nember of active connections to reduce its memory footprint, or to improve performance for other clients. Most firewalls and networks let you keep your connections alive for as long as you wish, but some may act up, and that’s when you can use Scott’s trick.

Tip: Change 5 to 240 or 300, so that instead of every 5 seconds, the keep-alive signal is sent only once in 4 or 5 minutes

Sorry it took me so long to post this useful tip, Scott.

Possibly related posts: (automatically generated)

• open sshd time out problem