01-10-2013
In HP-UX zombie processes which are waiting for a hardware resource will not die without a reboot.
Can you post an example process tree?
How many zombie processes do you have on a bad day? Do they ever disappear without a reboot?
What database engine are you using, and do you have a simple explanation for the zombie processes (like users disconnecting untidily)?
This User Gave Thanks to methyl For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I ps -ef I see about 3 or 4 <DEFUNCT> things - what are these, and what causes them? Are they a concern? How can I fix them?
Thanks,
Michael (4 Replies)
Discussion started by: cuppjr
4 Replies
2. Solaris
mqm 17700 16815 0 0:00 <defunct>
kill -9 does not work, even as root (10 Replies)
Discussion started by: csaunders
10 Replies
3. UNIX for Dummies Questions & Answers
Hey guys/gals. I am new to the site and fairly new to Unix/Linux. I have a master netbackup server (solaris) that I get pinged on occasionally regarding defunct processes. (Usually over 50 or so of them.) I know what a defunct process is, but what is it a product of? Just plain sloppy code? (From... (1 Reply)
Discussion started by: EMCSANMAN
1 Replies
4. UNIX for Dummies Questions & Answers
can some one please explain
zombie
orphan
defunct
and how they r related (3 Replies)
Discussion started by: pbsrinivas
3 Replies
5. AIX
Hi,
Can any one help me to get rid of defunct process on UNIX IBM AIX box. These processes started when the system was rebooted almost after 1 1/2 years. Once one defunct process is created then all the user ids get infected and in turn creates numerous defunct processes. We have tried... (6 Replies)
Discussion started by: trokia88
6 Replies
6. Programming
hello everybody!
Is there any way to identify if a process is defunct or if it is still running? (in C).
for example: by using a signal such as SIGCHLD?
thanx in advance (1 Reply)
Discussion started by: nicos
1 Replies
7. Shell Programming and Scripting
Hi All,
Sorry to bother you all if my query is silly. Can you please clarify my doubts on defunct processes.
Actually coming to the scenario, i have a server which is under cluster environment. Server B is having problems with the defunct process. There was a cron scheduled on Server B which... (0 Replies)
Discussion started by: reddybs
0 Replies
8. HP-UX
Dear Sir / Madam,
We have two socket programs which are running in background. These two socket programs are creating defunct processes in HP-UX which were not happening in Compaq True64 UNIX. What is the root cause of these defunct processes and how can we correct it?
Your suggestion will be... (3 Replies)
Discussion started by: kcsahoo
3 Replies
9. UNIX for Advanced & Expert Users
HiI had a tool fail recently, on analysis I found it was cleaning up orphaned directories that had been created by specific processes that had died for some reason, thus failing to clean up after themselves.The directories were of the form /dir.pid. The tool would look to see if any instances of... (2 Replies)
Discussion started by: steadyonabix
2 Replies
10. HP-UX
I'd like to remove this defunct processes without rebooting. Or, I could remove this defuncts when the maximum allowable process is nearly reached, then send an email to the user/team. How can I determine the maximum allowable process that a server can handle? Any thoughts?
Jin@PRODUCTION: >... (3 Replies)
Discussion started by: Jin_
3 Replies
reboot(1M) reboot(1M)
NAME
reboot - reboot the system
SYNOPSIS
time] message]
time] message]
DESCRIPTION
The command terminates all currently executing processes except those essential to the system, then reboots the system, or halts, or makes
the partition ready for reconfiguration. When invoked without arguments, syncs all disks before rebooting the system.
Options
The command recognizes the following options:
Shut down the system and halt.
Shut down the system and reboot automatically (default).
Shut down the system to a ready-to-reconfigure state and reboot if possible.
If the partition is unable to reboot, it will stop at a ready-to-reconfigure state. However, if the option is also
specified, the system will always stop at ready-to-reconfigure state. This option is available only on systems that
support hardware partitions.
Shut down the system to a ready-to-reconfigure state and do not reboot.
This option can be used only in combination with the option. This option is available only on systems that support
hardware partitions.
Do not sync the file systems before shutdown.
The and options are ignored with this option.
Sync the file systems before shutdown;
for file systems that were cleanly mounted, modify the flag from to (default).
Quick and quiet.
Suppress broadcast of warning messages, terminate processes by brute force (with and immediately call with arguments
as indicated by the other options (see reboot(2)). No logging is performed. The and options are ignored with this
option.
Specify what time
will bring the system down. time can be the word (indicating immediate shutdown) or a future time in one of two for-
mats: and The first form brings the system down in number minutes; the second brings the system down at the time of
day indicated (based on a 24-hour clock).
Display message at the terminals of all users on the system at decreasing intervals as reboot time approaches. The message
must not contain any embedded double quotes.
At shutdown time a message is written in the file
(if it exists), containing the time of shutdown, who ran and the reason.
Only users with appropriate privileges can execute the command.
WARNINGS
does not invoke the shutdown scripts associated with subsystems to bring them down in a cautious manner. See shutdown(1M).
If the option is used in a virtual partition environment on a partitionable system, then the requested reconfiguration will not take place
until all the virtual partitions on that hard partition are shut down and the virtual partition monitor is rebooted.
AUTHOR
was developed by HP and the University of California, Berkeley.
FILES
Shutdown log
SEE ALSO
vpartition(1), reboot(2), partition(5).
reboot(1M)