![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| pid of nohup process | rein | Shell Programming and Scripting | 2 | 10-23-2007 03:42 PM |
| nohup process hangs | Sully | Shell Programming and Scripting | 2 | 11-02-2005 01:53 PM |
| background process | zylwyz | UNIX for Dummies Questions & Answers | 5 | 07-12-2005 12:17 PM |
| background process | badshah | High Level Programming | 3 | 05-30-2003 08:01 AM |
| capture the process id when starting a background process | jleavitt | Shell Programming and Scripting | 10 | 04-04-2002 05:04 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
nohup and background process
What is the difference between running a process using nohup and running a process in background ? Please explain
|
| Forum Sponsor | ||
|
|
|
#2
|
|||
|
|||
|
Hi,
nohup - no hangup when you suffix with & for running some task, this task will run in background. example cat ex.txt|sort & if you want to continue this job after you log out from your terminal, you can prefix with nohup nohup cat ex.txt|nohup sort & Thanks, Shahnaz. |
|
#3
|
|||
|
|||
|
difference between nohup and &
what is the difference between nohup and & say
1)nohup cat test.dat and 2)cat test.dat & and 3) nohup cat test.dat & By nohup you say no hangup, what do you mean by no hangup? Please explain more Thanks |
|
#4
|
||||
|
||||
|
Quote:
Code:
Run a command immune to hangups, runs the given COMMAND with hangup signals ignored, so that the command can continue running in the background after you log out. Code:
`nohup' does not automatically put the command it runs in the background; you must do that explicitly, by ending the command line with an `&'. |
|
#5
|
|||
|
|||
|
Quote:
Then that controlling terminal closes it sends the processes under it's umbrella a 'SIGHUP' signal, this will normally kill those processes. 'nohup' traps this signal and may detach from the controlling terminal. |
|||
| Google The UNIX and Linux Forums |