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(8) System Manager's Manual reboot(8)
NAME
reboot - Restarts the machine
SYNOPSIS
/usr/sbin/reboot [-dlnq]
DESCRIPTION
When the system is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation. If no users are
logged in, use the reboot command.
The reboot command normally stops all running processes, syncs the disks, logs the reboot, and writes a shutdown entry in the login
accounting file, /var/adm/wtmp.
The reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard-
ware time-of-day clock. After these activities, the system reboots. By default, the system starts and the file systems are automatically
checked. If the start-up activities are successful, the system comes up in the default run-level.
You must have root privileges to use this command. Using the -n flag can result in file system damage.
FLAGS
Generates a crash dump of the system before halting it. Can be used with any of the other flags. Does not log the reboot using syslog
Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not log
the reboot using syslog
EXAMPLES
To enable the default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the
shutdown, and perform other routine shutdown and reboot activities. To shut down the system without logging the reboot, enter: reboot -l
This command shuts down the system and performs all shutdown and reboot activities, except logging the shutdown. To reboot the system
abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes.
FILES
Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon
RELATED INFORMATION
Commands: fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8)
Functions: reboot(2), sync(2), syslog(3) delim off
reboot(8)