topic Re: remsh not backgrounding with nohup and "&" on 11.0 in Operating System - HP-UX

remsh not backgrounding with nohup and "&" on 11.0

jerry1 — Mon, 18 Oct 2004 11:59:52 GMT

I have noticed that doing a remsh to HP-UX 11.0
when trying to spwan off a background process that won't die when you exit. example:

exec nohup &

That the script waits till the process is done.

This is only when trying to remsh to an HP-UX
11.0 OS. HP-UX 11i does not have this problem.
The process is backgrounded and the remsh exits.

Here is a simple example:

Script A:

#!/bin/ksh
# scripta
remsh $1 ./scriptb

Script B:

#!/bin/ksh
#scriptb
exec nohup sleep 10 &

Run script A to hp-ux 11.0 and 11i system:

scripta

scripta

Can someone tell me why this behavior is different between 11.0 and 11i?

I need to be able to remsh into serveral
systems and run a continual process in the backgrond.

Re: remsh not backgrounding with nohup and "&" on 11.0

Scot Bean — Mon, 18 Oct 2004 12:05:44 GMT

"man remsh" recommends the following synyax to run a remote cmd that does not wait for the return:

remsh otherhost -n "command 1>&- 2>&- &"

Re: remsh not backgrounding with nohup and "&" on 11.0

Sridhar Bhaskarla — Mon, 18 Oct 2004 13:05:04 GMT

Hi Jerry,

Scott got it. Use '-n' option with the command as it redirects input from /dev/null instead of the shell to wait for input from the keyboard.

-Sri

Re: remsh not backgrounding with nohup and "&" on 11.0

Dietmar Konermann — Wed, 20 Oct 2004 03:01:24 GMT

The described behaviour has been changed several times with patches... on both, 11.00 and 11.11, afaik.

The current behaviour (recent r-commands patches installed) is:

- wait (default)
- don't wait (if remshd is called wirth new -m option)

So I suggest to simply install recent patches and then use -m to get the desired behaviour.

11.00: PHNE_23003
11.11: PHNE_30433

Best regards...
Dietmar.

Re: remsh not backgrounding with nohup and "&" on 11.0

Muthukumar_5 — Wed, 20 Oct 2004 03:43:32 GMT

It will be expecting users input to stop the exec nohup sleep 10& on remote node.

You can try as,

remsh -n "command 1 1>/tmp/remotelog.log1 2>&1 &; command 2 1>/tmp/remotelog.log2 2>&1 &"

Or change the code of script B as,
#!/bin/ksh
#scriptb
exec nohup sleep 10 1>/tmp/log 2>&1 &

Else simply,

#!/bin/ksh
#scriptb
exec nohup sleep 10 1>&- 2>&- &

so that it will not expect user input to upon completion of sleep 10 execution.

HTH.