The death of a process, even a parent process, does not trigger the kernel to send SIGHUP to any processes. That only happens when the controlling terminal/pseudo terminal is hung up/closed. If SIGHUP is not the signal being sent, nohup will not prevent a process dying if that is the default action for whatever signal it is actually being sent (a SIGINT or SIGTERM will still kill a process, unless they're explicitly trapped by the receiving process).
Default behavior when a SIGHUP signal is sent to a process is for the kernel to terminate the process. nohup simply sets the SIGHUP signal to be ignored and then execs its argument (the command you want to run, which then inherits this signal handling modification from nohup ... all other singal handling is unmodified).
Hi everybody,
I'm trying to understand how a parent and child processes interact.
This function( below) basically measures the fork time from the perspective of the parent only.
what i would like to know is how to measure the time from the perspective of parent and child (ie: inserting... (0 Replies)
Hi
I am trying to see if there are some options in ps command or if there is a shell script which basically shows you all the processes spawned by a parent process , then all the processes of its child processes and so on down the hierarchy may be like a tree structure. It might be a generic... (6 Replies)
Hi
I want to do something that might sound strange.
I have a code that in written in C and is executed at startup (it's a custom process). It occasionally calls some bash scripts.
The process doesn't have any terminal associated with it.
One thing I don't know how to do is to start a... (5 Replies)
Hi All,
I have two ksh script. 1st script calls the 2nd script and the second script calls an 'C' program.
I want 1st script to wait until the 'C' program completes.
I cant able to get the process id for the 'C' program (child process) to make the 1st script to wait for the second... (7 Replies)
Hi guys, I'm having some problem here, I'm studying pipes, and i want to create a shell in C and at this point a don't want to use semaphores, instead I want to use tricks. Straight to the doubt: I've a parent and a child process, and both of them has some code to execute, and the child process... (5 Replies)
Hi,
I have a script that calls other scripts/commands which may or may not spawn other process.
From my understanding, when I do a ps -ef, the highest numbered process ID is supposed to be the parent ID of all the other related child processes, is this correct?
In most or all... (3 Replies)
Hi, i want that the parent process start before the child, this code doesn't work,
if the child start before the parent it wait for signal, then the father send the signal SIGALRM and the child catch it and call printf;
else the father call printf and send the signal to the child that call its... (1 Reply)
Hello, everyone.
Here's a program:
pid_t pid = fork();
if (0 == pid) // child process
{
execvp ...;
}
I send a signal (such as SIGINT) to the parent process, the child process receive the signal as well as the parent process.
However I don't want to child process to receive the... (7 Replies)
Hi everyone
i am very new to linux , working on bash shell.
I am trying to solve the given problem
1. Create a process and then create children using fork
2. Check the Status of the application for successful running.
3. Kill all the process(threads) except parent and first child... (2 Replies)
HI i would like to know how i can simulate a shell scripts for my requirement.
example
Server name child Process id Parent Process id
Vpesh 16013 15637
Server name child Process id Parent Process id
Vpesh 16014 15637
Server name child... (1 Reply)
Discussion started by: vpesh
1 Replies
LEARN ABOUT BSD
nohup
NICE(1) General Commands Manual NICE(1)NAME
nice, nohup - run a command at low priority (sh only)
SYNOPSIS
nice [ -number ] command [ arguments ]
nohup command [ arguments ]
DESCRIPTION
Nice executes command with low scheduling priority. If the number argument is present, the priority is incremented (higher numbers mean
lower priorities) by that amount up to a limit of 20. The default number is 10.
The super-user may run commands with priority higher than normal by using a negative priority, e.g. `--10'.
Nohup executes command immune to hangup and terminate signals from the controlling terminal. The priority is incremented by 5. Nohup
should be invoked from the shell with `&' in order to prevent it from responding to interrupts by or stealing the input from the next per-
son who logs in on the same terminal.
FILES
nohup.out standard output and standard error file under nohup
SEE ALSO csh(1), setpriority(2), renice(8)DIAGNOSTICS
Nice returns the exit status of the subject command.
BUGS
Nice and nohup are particular to sh(1). If you use csh(1), then commands executed with ``&'' are automatically immune to hangup signals
while in the background. There is a builtin command nohup which provides immunity from terminate, but it does not redirect output to
nohup.out.
Nice is built into csh(1) with a slightly different syntax than described here. The form ``nice +10'' nices to positive nice, and ``nice
-10'' can be used by the super-user to give a process more of the processor.
4th Berkeley Distribution May 8, 1986 NICE(1)