waitpid and grandchildren Post: 302642877

Sponsored Content

Top Forums Programming waitpid and grandchildren Post 302642877 by otheus on Friday 18th of May 2012 06:35:48 AM

05-18-2012

Registered User

Quote:

Once I get the final PID of the daemon in question, I detach from it with a PTRACE_DETACH and let it run unhindered.

My understanding is that once you detach a process, you no longer get signals like SIGCHLD on its behalf.

But the idea of using ptrace for this kind of thing seems novel to me.

Quote:

can I monitor a given grandchild process without becoming the init process

. DJ Bernstein's Daemontools offers a solution. You leave a file-descriptor open to the grandparent (so your monitoring program never truly detaches).

otheus

View Public Profile for otheus

Find all posts by otheus

3 More Discussions You Might Find Interesting

1. Programming

problems with FORK() and WAITPID()

Dear All, I'm trying to write multithreading TCP Daemon which executes external program when new network connection arrives on a socket. After accept() I'm doing fork() for initiating of new child process, in which will be executed external program. After child creation I'm doing fork() again,...

2. Programming

waiting for multiple childs - C - waitpid

Hi gurus, I would like to fork more children and then write their return values: so far I tried: #include <stdio.h> #include <stdlib.h> #include <errno.h> #include <unistd.h> #include <sys/types.h> #include <sys/wait.h> int main(void) { pid_t pid; int rv=0, i; ...

3. Programming

[C]Fork and waitpid

Hi folks, I am writing a simple program to understand how fork() and waitpid works, but it doesn't seem that is working like I wanted. if(fork()==0){ //el hijo pid1=getpid(); printf("\nSoy el hijo %d",pid1); }else { //el padre if (fork()==0) { //el hijo pid2=getpid();...

LEARN ABOUT OSF1

statd

rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME

       rpc.statd, statd - Network status monitor daemon

SYNOPSIS

       /usr/sbin/rpc.statd [-c]

OPTIONS

       Available only on TruCluster Server systems. This option starts the clusterwide network status daemon, which helps provide highly available
       NFS service. Do not use -c directly. Highly available NFS service is configured by default and typically does not require intervention.	If
       you do need to start the clusterwide network status daemon, use the CAA command, caa_start cluster_lockd.

	      For more information, see the TruCluster Server Administration manual.

DESCRIPTION

       The  rpc.statd daemon monitors the status of the client and server sites in response to a request made by the local rpc.lockd daemon.  When
       a site failure is detected, the rpc.statd daemon notifies the local rpc.lockd daemon, which then processes the recovery of the locked files
       or file regions.

RESTRICTIONS

       The crash of a site is only detected on its recovery.

FILES

       A directory created by the statd daemon.  Each file name in the directory is the host name of a client or server that the statd daemon will
       notify upon its recovery.  A backup directory created by the statd daemon.  A file created by the statd daemon to store its state number.

SEE ALSO

       Daemons: rpc.lockd(8)

       Files: statmon(4)

																      rpc.statd(8)