Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to run a job on remote server with no login. I found that I can run my job using ssh as:

ssh remotenode -t /path/to/myjob &> /path/to/log

However, the job would be killed by Signal 15 after a while. Does SSH force some timeout?

NOTE: My jobs takes a few hours to be completed.

share|improve this question
up vote 3 down vote accepted

If I may suggest using screen

ssh remotenode -t "screen -S ServerFault top" 

This will start screened top process with session name 'ServerFault' . Later on you can simply re-attach this on remotenode using

screen -r ServerFault

share|improve this answer
Thanks. Then should I run the job as ssh remotenode -t "screen -S ServerFault /path/to/myjob &> /path/to/log " ? – ahmad Oct 8 '12 at 4:52
no need for &; just ctrl+a+d to detach screen and process will be left running on remotenode until you ssh to remotenode and run 'screen -r ServerFault' to check what is happening with your process – Hrvoje Špoljar Oct 8 '12 at 10:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.