How to Clean up an Orphan Process in HP-UX?

Suppose we have a process, and it forks a child process, in HP-UX 10.0.  If the parent terminates (in an unexpected way), we may want to let that orphan child process exit.  How can this be implemented?  Or in other words, how can the child process know its parent has terminated?  (It seems signal SIGHUP doesn't work, and the system doesn't clean up it in a short time.)
cheng060397Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

beckers012097Commented:
Where are you trying to handle the SIGHUP in parent- or child-process? Normally the signal-handling in HP-UX is very clean an works fine...
0
cheng060397Author Commented:
Thanks, Beckers!  What I understand is that SIGHUP is generated when parent process terminates.  So I let child handle it, but it turned out that the child couldn't receive that signal.  (If the child called kill(getpid(), SIGTSTP) to suspend itself, it would receive it. (See Stevens' book, pages 256-258.)  But no one wants to suspend the child.)  My code looks like:
   
void main()
{
    childpid = fork();    
    if (childpid == -1) {
      perror("fork error\n");
      exit(0);
    }
    else if(childpid == 0) {                   /* child */      
        signal(SIGHUP, sig_func);
        /* some child code here */
    }                                           
    else {                                 /* parent */
        /* some parent code here */
    }
}

void sig_func()                             /* signal handler */
{
    printf("SIGHUP received.\n");
    exit(1);
}

0
beckers012097Commented:
Try using a signal-handler in parent-process (for all fatal signals like SIGKILL, SIGSEV etc.). In this signal handler shut down the child-process (you know the pid from fork) by sending a "soft"-kill. Then after recieving the childs exit-status terminate the parent-process.

But I don't understand the reason for not getting SIGHUP...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

cheng060397Author Commented:
Thanks, beckers, but I am not sure those fatal signals can cover all unexpected terminations.
0
beckers012097Commented:
They should, there are no other reasons for terminating a program than the signals you can catch. Or I understood it wrong for 10 years... Catch all signals?!?
0
cheng060397Author Commented:
Thanks, beckers!

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.