Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-31-2009, 08:47 AM
|
#1
|
Member
Registered: Nov 2008
Location: Egypt
Posts: 110
Rep:
|
Close terminal during applying patch . . .
Dears,,
During applying Oracle Patch in Linux,
I closed the terminal by mistake.
Is this stop the applying patch process?
Thanks,,
|
|
|
03-31-2009, 11:59 AM
|
#2
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,794
|
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??
|
|
|
04-01-2009, 03:51 AM
|
#3
|
Member
Registered: Nov 2008
Location: Egypt
Posts: 110
Original Poster
Rep:
|
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,,
|
|
|
04-01-2009, 05:01 AM
|
#4
|
Senior Member
Registered: Sep 2003
Location: UK
Distribution: Debian
Posts: 1,215
Rep:
|
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.
|
Last edited by lugoteehalt; 04-01-2009 at 05:04 AM.
|
|
|
04-01-2009, 05:45 AM
|
#5
|
Member
Registered: Nov 2008
Location: Egypt
Posts: 110
Original Poster
Rep:
|
Many thanks for clarifications . . .
Best regards,,
|
|
|
04-01-2009, 09:24 AM
|
#6
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,794
|
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.
|
|
|
All times are GMT -5. The time now is 04:09 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|