Hi,

I had started a process which was supposed to be of few minute but due to some reason I hv to run it for 2-3 days without stopping it. I am accessing it using SSH, as I was not aware that It has to run from long.. I did not use "SCREEN" utility or "NOHUP" but now I need it to be running in background.

Since its already running, I can't use Screen and nohup and can't restart it as it will be waste of many hours already used.

so wht I find solution is using
CTRL + Z and then send it to background using
bg 1

but I guess when I will close that SSH window then It will stop that background JOB.

I m running a scrip on large database, if it stops then has to start all over. So without stopping it want to send to background so that I can turnoff my computer here or if some problem in conection then wont' stop that process..

Its realy urgent for me!

Probably, although that is not certain. When happens is that the process will receive the signal SIGHUP (hang up). Most programs do the default action with this signal - to abort the program - but if the programmer chose to intercept the signal and do something else with it (or ignore it) the program may not quit.

Having said all that, it is probably prudent to assume that SIGHUP will cause the program to terminate.

[QUOTE=Ricky;2972243]I m running a scrip on large database, if it stops then has to start all over. So without stopping it want to send to background so that I can turnoff my computer here or if some problem in conection then wont' stop that process..

I don't think that helps get a question answered any more quickly. People will only answer if they can, and a question is interesting.

In any case, assuming you are using bash as your interactive shell on the remote host, you can use the disown builtin.

HI methew.. dont' mind about my "urgency" word ..
so you mean using ctl+z said might be risky as it may cause program to terminate... hmm..

So how I use disown ....
I am running process with PID 8769 in other terminal, then I logged into other terminal, typed
Shall it work this way and wont' stop execution of that process ?

No, I mean when you close the connection... that is when SIGHUP is sent to all jobs running from that shell (i.e. backgrounded processes).

Usage information can be found in the bash manual page. Essentially you need to specify the job spec which you wish to disown. You can see a list of background job ids by running "jobs".

If you are uncertain, do a test with another process first to verify you have the proper syntax.

You can also unset the huponexit shopt. To see the current setting of huponexit, do this:
If the setting is "on", it means SIGHUP will be sent to the backgrounded processes when the shell terminates. You can turn it off like this:
Note the huponexit setting only applies to login shells. This probably does apply to your ssh session.

nevermind.. I had to restart that proces.. now I am running it under screen .. doing fine !

though disown <PID> is correct syntax.. today wholeday I was playing with similar stuff to understand their behaviour !