luhman.org

Depending on the environment you're working in, you may be automatically logged out from a server by SSH timeouts. Here are a few things you can do to help prevent these timeouts :

Add or modify the following in your /etc/ssh/sshd_config file :

ClientAliveInterval 28800
ClientAliveCountMax 28800

In your ~/.bashrc file, set the TMOUT parameter to something longer. For example :

export TMOUT=28800

On your client (PuTTY) set the seconds between keepalives to something like 30.

jEdit has a nice SFTP plugin which allows you to edit remote files as if they're on your local machine.

I've been working with the Netbeans IDE lately. It's nice, but lacking a decent SFTP plugin.

A little searching revealed Dokan which allows you to build a ssh file system on your Windows machine.

Setup is a bit awkward. You need two downloads. One is the needed libraries, the other is a simple app/GUI which allows you to mount the remote file system as Windows drive letters N:, T: etc.

So far it seems to work as advertised. And free!

http://dokan-dev.net/en/download/

The other day I was downloading several podcasts from the net, while doing an expensive rsync across my slow home network. My dual core CPU was showing 50% on one CPU, about 0% on the other, and my network was shown at about 1%.

My iTunes had a "download multiple streams" checkbox that was unchecked. I thought running multiple streams might actually slow things down due to thrashing/context switching, but I checked it to give me multiple streams.

When upgrading servers, you may encounter this question : Should we stay at at 32-bit OS, or 'upgrade' to a 64-bit OS?

To me, the big advantage of a 64-bit OS is the ability to address (use) more than 4 gigabytes of RAM. I sometimes bump into that limit on my desktop,
so I think it's best to have a 64 bit OS for servers.

Larger memory space isn't the only advantage, however. From Wikipedia :