09-09-2008
I have seen this type of problem after a reboot in the following circumstances (granted, it was Solaris, but the principle is the same):
1. Server is booted
2. A new filesystem is mounted, but not updated in vfstab
3. A utility to do some task (like cleanup) is called from the new filesystem
4. Server is rebooted
5. The filesystem is not mounted at boot time
6. The utility is called to perform the cleanup task - but there's nothing there.
7. The application crashes quietly, you end up with defunct processes.
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. Programming
how can i assure that daemon process which is being run as init child,can be removed immediately from system when it goes defunct or to avoid daemon process becoming defunt? (5 Replies)
Discussion started by: rish2005
5 Replies
3. Solaris
mqm 17700 16815 0 0:00 <defunct>
kill -9 does not work, even as root (10 Replies)
Discussion started by: csaunders
10 Replies
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. HP-UX
How to find out and clear the 'defunct' processes at OS and DB level ..?? (6 Replies)
Discussion started by: SurajR
6 Replies
LEARN ABOUT FREEBSD
autounmountd
AUTOUNMOUNTD(8) BSD System Manager's Manual AUTOUNMOUNTD(8)
NAME
autounmountd -- daemon unmounting automounted filesystems
SYNOPSIS
autounmountd [-d] [-r time] [-t time] [-v]
DESCRIPTION
The autounmountd daemon is responsible for unmounting filesystems mounted by automountd(8). On startup, autounmountd retrieves a list of
filesystems that have the automounted mount option set. The list is updated every time a filesystem is mounted or unmounted. After a speci-
fied time passes, autounmountd attempts to unmount a filesystem, retrying after some time if necessary.
These options are available:
-d Debug mode: increase verbosity and do not daemonize.
-r Number of seconds to wait before trying to unmount an expired filesystem after a previous attempt failed, possibly due to filesystem
being busy. The default value is 600, or ten minutes.
-t Number of seconds to wait before trying to unmount a filesystem. The default value is 600, or ten minutes.
-v Increase verbosity.
EXIT STATUS
The autounmountd utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
auto_master(5), autofs(5), automount(8), automountd(8)
HISTORY
The autounmountd daemon appeared in FreeBSD 10.1.
AUTHORS
The autounmountd was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.
BSD
December 13, 2014 BSD