- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: lingo
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 01:25 PM
08-02-2001 01:25 PM
lingo
i have seen admins/books say different things for each, and i am at the point where i do not know who is right/wrong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 01:31 PM
08-02-2001 01:31 PM
Re: lingo
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xa26e87dc4d7dd5118ff00090279cd0f9,00.html
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 02:51 PM
08-02-2001 02:51 PM
Re: lingo
for the response(s) by Magdi.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xa26e87dc4d7dd5118ff00090279cd0f9
-Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 03:42 PM
08-02-2001 03:42 PM
Re: lingo
There are a few of posts which maybe are useful for you.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x6f717e990647d4118fee0090279cd0f9,00.html
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xa26e87dc4d7dd5118ff00090279cd0f9,00.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 11:22 PM
08-02-2001 11:22 PM
Re: lingo
Zombie process are those ones that when they finish working ( normal or abnormal exit ) they didn't find their parents executing a wait() function( waiting ) for them.
That's mean, consider a process P0 is doing a fork ( creates a copy of himeself ). The copy process is P1 called the child process ( so P0 is the parent process of P1 ).
If P1 finish his work ( normal or abnormal exit ) and P0 is not listening to him with a wait() function. So , P1 became a ZOMBIE process.
Alot of devellopers fall into this problem ( they are no more accepted into the system under their loginnames till these zambies are killed with a BOOT of course ) and the only way to kill them is REBOOTING the system.
Why booting, is that Zombies are considered as
1. Not live nor Died !!! So how to kill them.
If you need any help to avoid this miss programming, I have the solution just append your request .
Have a look in the following book :
Advanced Programming in the UNIX Environment.
Addison-Wesley
W. Richard Stevens.
Pages 195 and 196
Example:
P0 is the parent of P1.
P1 is the child of P0.
Normal programming is :
1. The parent P0 should execute a wait() function before a child process terminates normally or abnormally.
2. If Child process is not sure that his parent is waiting for him , he will execute the function getppid() function and executes an exit() as soon the function getppid() returns 1 ( that means that the unix init process (pid 1) is the actual parent).
unix init process ( pid 1) inheriets all orphan processes and immediately executes a wait() function as soon as a child process exits ( normal or abnormal exit ).
It's really the Client/Server model from a process point of view .
The manner by which the Unix model avoid that is :
P0 forks twice ,
P0 fork and gives P1
P1 fork and gives P2
1.The first instruction of P2 is to loop till getppid() returns 1; getppid means GetParentProcessIdentification. ( init process )
2. The first instruction of P1 is exit() function.
3. P2 became ORPHAN.
4. init process become the actual parent of P2.
5. The function getppid() returns 1 now.
6. The P2 process executes its task.
7. P2 terminates normally or abnormally.
8. init process executes an immediate wait() function.
9. P2 died without being ZAMBIE.
If you follow this protocol, your application will never have zombies processes.
Hope this explain the issue.
Wainting for any discussion.
Magdi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2001 04:38 PM
08-03-2001 04:38 PM
Re: lingo
at this point i think the following
zombies: cannot communicate with parent, cannot be killed (only reboot clears), shows up in "ps" as
orphans: cannot communicate with its parent, but if init becomes the parent there is a chance for it to die/exit without turning into a zombie
defunct: zombie
runaway: shows up possibly in "ps" as R for state, is able to be killed, only a CPU hog with high values for TIME in "ps"
wondering if my simplified summary is OK? is missing any basic key concept, etc.?
wondering also if there were some other ways to identify zombies/orphans, to terminate orphans (like using special kill signals), and to possibly get early signs of runaways/potential runaways?
thx in advance for any input, and to those who have already replied