topic Re: nohup question in Operating System - HP-UX

nohup question

Ignite_2 — Fri, 20 Mar 2009 19:05:23 GMT

Hello,

could you please help me...

Is it possible to apply 'nohup' on process running in foreground, to let it continue after logout?

Thanks in advance

Re: nohup question

Dennis Handly — Fri, 20 Mar 2009 19:46:13 GMT

Typically you use nohup to put it in the background:
nohup command &

Re: nohup question

Ignite_2 — Fri, 20 Mar 2009 19:52:40 GMT

Hi

yes, normally it's like that.

I have started copying data and didn't expected it can take so long.

Is there any possibility, how to apply on running process from another session 'nohup'?

Re: nohup question

Dennis Handly — Fri, 20 Mar 2009 20:23:24 GMT

>how to apply on running process from another session 'nohup'?

I don't know of any.

Re: nohup question

Johnson Punniyalingam — Sat, 21 Mar 2009 00:44:09 GMT

Hi,

You can put "all the required files to copied " in script. than you can let it continue after logout?

Example:-

# vi copy.sh
cp -p /opt/oracle/dbf* /opt/oracle/source

# nohup ./copy.sh &

Hope this helps,

Thanks,
JOhnson

Re: nohup question

Ski Ride — Sat, 21 Mar 2009 05:07:15 GMT

Hi Ignite

I believe you cannot use nohub on a process that is already running.

I believe this is wat is ur question.

Re: nohup question

sujit kumar singh — Sat, 21 Mar 2009 10:25:50 GMT

Hi

This is alwayu suggested to start a process with a nohup as in your case so that the process keeps up running in case the executing terminal is logged out or killed.
regards
sujit

Re: nohup question

hbhua_231 — Mon, 23 Mar 2009 05:57:41 GMT

I found that if you invoked another shell, then ran the nohup script, then exited your child shell, the nohup would continue to run properly.

sh
nohup sar -u 5 5 &
exit

------------------------
good luck.

Re: nohup question

Heironimus — Mon, 23 Mar 2009 15:08:04 GMT

If your shell is modern enough you can ctrl-Z to suspend the foreground process, "bg" to resume it in the background, and "disown %jobnum" to tell the shell to forget about it and not send a SIGHUP on exit. A little more to type, but it produces the same end result as running via nohup.