Welcome to the Linux Foundation Forum!

Why my shell script is always "stopped" ?


This is the problem that drives me crazy. I let a script A (a.sh) call script B (b.sh).

I used

nohup a.sh &>/tmp/log &

In script A it calls B directly, without any redirecting or nohup or background.

Script A:

#do nothing but call B
ssh another-machine "/user/tom/b.sh"

Script B:

# do some fancy things, takes about 1 hour to finish

I used

nohup a.sh &>/tmp/log &

It was "stopped" after 5 minutes but B was running and B finished correctly.

Anybody knows why?

BTW, if I don't use nohup and backgrounding, it's OK. i.e. if I use


directly. Everything is OK. I am totally confused.


  • ludovic.ferre
    Have you check if this is just the ssh session timing out on your remote machine?

    You are calling the program with nohup, but that applies locally, doesn't it?
  • woboyle
    woboyle Posts: 501
    ssh requires that stdin, stdout, and stderr (all the stdio stuff) be associated with a valid file or device handle. When you run in the foreground, it will take these from the shell (the tty you are running on). When run in the background, there is no stdin, so in your case you will need to redirect the input. If the file "/user/tom/b.sh" is on your local machine, then try this
    ssh another-machine <"/user/tom/b.sh"

    in order to redirect stdin appropriately. Don't know if it will work for sure, but it should.


Upcoming Training