Close terminal during applying patch . . .

eng_mohammedmostafa · 03-31-2009, 08:47 AM

Dears,,

During applying Oracle Patch in Linux,
I closed the terminal by mistake.

Is this stop the applying patch process?

Thanks,,

TB0ne · 03-31-2009, 11:59 AM

Quote:

Originally Posted by eng_mohammedmostafa

Dears,,

During applying Oracle Patch in Linux,
I closed the terminal by mistake.

Is this stop the applying patch process?

Thanks,,

Yes, since you killed the process that was running, unless you nohup'ed and backgrounded it.

And did you look to see if it completed afterwards, which would tell you if it finished or not??

eng_mohammedmostafa · 04-01-2009, 03:51 AM

Dear

I understood from you that the process stopped since i closed the terminal.
What is the command that enable me to background the process to keep it running even i closed the terminal?
Is there a command show me the processes that are running now?

Thanks,,

lugoteehalt · 04-01-2009, 05:01 AM

Put something in background by putting a & after it. E.g. $ eaglemode &

Another thing is ctrl+z. See other jobs with $ jobs. Go to a job, with %n where n is the number of the job - you get this number from $ jobs.

Quote:

nohup(1) - Linux man page
Name
nohup - run a command immune to hangups, with output to a non-tty
Synopsis
nohup COMMAND [ARG]...
nohup OPTION
Description

Run COMMAND, ignoring hangup signals.

--help
display this help and exit
--version
output version information and exit

NOTE: your shell may have its own version of nohup, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports.

eng_mohammedmostafa · 04-01-2009, 05:45 AM

Many thanks for clarifications . . .
Best regards,,

TB0ne · 04-01-2009, 09:24 AM

Quote:

Originally Posted by lugoteehalt

Put something in background by putting a & after it. E.g. $ eaglemode &

Another thing is ctrl+z. See other jobs with $ jobs. Go to a job, with %n where n is the number of the job - you get this number from $ jobs.

That will put it in the background, yes. But if you do that, and close the terminal window you started it in, the job will still stop, because you killed the parent process.

To keep the job running, regardless of killing the terminal window or not, you have to start it with a nohup (I mentioned it in my first post), such as "nohup myjob &". That will start a new parent process, and put the whole thing in the background, making it totally independent of the parent terminal.