Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Is orphan process handling by Solaris os and Linux os same? Post 302997103 by Don Cragun on Monday 8th of May 2017 04:44:49 AM
Old 05-08-2017
Moderator's Comments:
Mod Comment This thread has been moved from the What is on Your Mind? forum to a technical forum.

You state in your post that Solaris systems and Linux systems behave completely differently when a parent process terminates without waiting for its children to terminate and then ask if they behave differently when a parent process terminates without waiting for its children to terminate??? Although I find it hard to believe that many of the differences that you stated as facts are true; if you believe that those facts are true, I do not understand why you are asking the question.

Is this a homework assignment?

What code are you running that exhibits the differences you are seeing on Solaris systems and Linux systems?

What Solaris release(s) are you using?

What Linux distribution(s) are you using? Which version(s) of those Linux distribution(s) are you using?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to kill stranded/orphan process by users.

I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
Discussion started by: rjohnson
4 Replies

2. HP-UX

Inter Process File Handling Problem

Hi All, i am running a oracle procedure which writes a file . The same file is picked up by another script which runs in a cron after every 5 minutes. Now the problem is that sometimes my script picks up a file while the procedure is still writing data in the file. is there is any way i... (4 Replies)
Discussion started by: saurabhjain
4 Replies

3. Programming

Linux g++ 2.95.3 exception handling

Anybody happen to be familiar with any deficiencies with g++ 2.95.3 regarding exception handling, specifically in multi-threaded / multi-module (shared library) based applications? I'm seeing behavior where thrown exceptions are not caught, but basically ignored causing the application to... (0 Replies)
Discussion started by: earl
0 Replies

4. Programming

handling abnormal process termination

hi i m writin a program in which i keep track of all the child processes the program has generated and if a child process has an abnormal termination i need to do certain task related to that child process. for handlin child process i used waitpid: temp_cpid=waitpid(-1,&stat,WUNTRACED); ... (4 Replies)
Discussion started by: mridula
4 Replies

5. UNIX for Advanced & Expert Users

how to remove db2 orphan processes

Hi Guys, I'm working on a AIX 5.3 environment and I've been quite a few times in a situation where we can remove db2 orphan processes therefore our only alternative has been to reboot the entire server. Now I wonder is there is any other possible way that we can use to remove those processes... (5 Replies)
Discussion started by: hariza
5 Replies

6. UNIX for Dummies Questions & Answers

Socket Handling Differences Between Linux & Unix?

Sorry if this is a stupid question! I have been developing a Java application that I am deploying on both Unix and Linux servers, which uses lots of socket handling. When the server side connection is dropped by the server un-gracefully I have been seeing close_waits and null connections. ... (0 Replies)
Discussion started by: Vinnie
0 Replies

7. Linux

Cron ORPHAN (no passwd entry)

I am using the standard vixie-cron am seeing the following my logs : crond: (username) ORPHAN (no passwd entry) Ordinarily this is a simple matter, there is no corresponding user, but I am using central authentication and the username does exist and is usable via the standard nsswitch mechanism, so... (2 Replies)
Discussion started by: humbletech99
2 Replies

8. Shell Programming and Scripting

Shell Script to Kill Process(number of process) Unix/Solaris

Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies

9. UNIX for Advanced & Expert Users

cronjobs orphan processes

Our cron job stats its started on Oct20 % ps -ef | grep cron root 1442044 1 0 Oct 20 - 25:23 /usr/sbin/cron All the below jobs aixmf,aixgh are triggered from cron only. user pid ppid date time cmd gaix 1581282 1 35 16:33:01 - 20:56... (1 Reply)
Discussion started by: karnan
1 Replies

10. Solaris

Handling inode on solaris 9

Dear all, yesterday I had a big problem on Solaris 9. I cannot write anymore on /var. I checked the inode usage, and I see that for /var was at 100% with ifree = 0. I deleted some unused files (like old log on /var/tmp and /var/log), now I have ifree=19641 and 99% iused: root@ciy01 # df -F ufs... (12 Replies)
Discussion started by: Lord Spectre
12 Replies
EXIT(2) 							System Calls Manual							   EXIT(2)

NAME
_exit - terminate a process SYNOPSIS
_exit(status) int status; DESCRIPTION
_exit terminates a process with the following consequences: All of the descriptors open in the calling process are closed. This may entail delays, for example, waiting for output to drain; a process in this state may not be killed, as it is already dying. If the parent process of the calling process is executing a wait or is interested in the SIGCHLD signal, then it is notified of the calling process's termination and the low-order eight bits of status are made available to it; see wait(2). The parent process ID of all of the calling process's existing child processes are also set to 1. This means that the initialization process (see intro(2)) inherits each of these processes as well. Any stopped children are restarted with a hangup signal (SIGHUP). Most C programs call the library routine exit(3), which performs cleanup actions in the standard I/O library before calling _exit. RETURN VALUE
This call never returns. SEE ALSO
fork(2), sigvec(2), wait(2), exit(3) 4th Berkeley Distribution May 22, 1986 EXIT(2)
All times are GMT -4. The time now is 12:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy