05-12-2009
Abnormal behaviour of Defuncts
Hi,
I am facing problems with defunct processes. The problem is, the defuncts are being created and getting dissappeared by themselves.
I have a process that calls some scripts through a specified port, when this scripts starts executing, the defuncts also started to appear(lots and lots, will be more than 1000 at times) and are getting dissappeared as soon as the scripts are completing. Those scripts collect system health info executing the commands like prstat, sar, etc..
This is happening only once in a day, at the time of these scripts getting executed.
This server is a part of cluster, hence i had checked the behaviuor in the other server where i couldn't find any problem with the scripts?
Is this some thing related to the performance of server?
It is normal that defuncts will appear when those scripts come into picture but only few(not more than 10).
Can anyone advise?
![Confused Smilie](https://www.unix.com/images/smilies/confused.gif)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm having trouble with Abnormal Termination errors. What are they, what causes them and how can I prevent them from happening? Are they application specific? (2 Replies)
Discussion started by: bialsibub
2 Replies
2. Programming
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
3. Filesystems, Disks and Memory
Hello, have a look my top and ps as below
Inact memory reach 1.6G, does it normal ?
load averages: 0.07, 0.02, 0.01; up 7+06:48:52 02:58:01
91 processes: 2 running, 89 sleeping
CPU states: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle
Memory: 24M... (0 Replies)
Discussion started by: jipznet1981
0 Replies
4. HP-UX
i am using HP-UX and i have this process called HPUX childwrapper taking about 99% cpu.i want to know what the process does? and if i should kill it (4 Replies)
Discussion started by: tomjones
4 Replies
5. 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
6. Shell Programming and Scripting
Hi,
facing unusual problem, below are 2 same scripts, one is working and other is not. please help
--- THIS SCRIPT IS WORKING FINE!!!!
#! /bin/sh
phone=`grep "<phone>" data.xml | sed 's:<phone>::;s:</phone>::'`
echo "Phone Number is:"$phone
repnum=554156
cat data.xml | sed -e... (3 Replies)
Discussion started by: Prateek007
3 Replies
7. BSD
Hi,
I have a bit of a headache with a server doing some rather mysterious yet static changes to permissions in /home. The server in question is a FreeBSD server. It's an older beast with quite a few custom tweaks and now I'm stuck with it :-)
The problem is that some of the directories in... (2 Replies)
Discussion started by: brightstorm
2 Replies
8. Shell Programming and Scripting
ok, so i have no clue why this script i wrote spits out these bizarre characters:
i cant even copy and paste those characters on here because it just doesn't show up properly.
my question is, using sed, how can i get rid of all characters that aren't normal?
echo "abnormal characters" |... (4 Replies)
Discussion started by: SkySmart
4 Replies
9. UNIX for Dummies Questions & Answers
i'm grepping for words in the /var/adm/messages (sun solaris).
but it looks like while my grepping finds the strings, when it outputs them out, the beginning of some lines are chopped off.
Jun 13 14:06:02 sky.net ufs: NOTICE: alloc: /prod: file system full
3 14:39:19 sky.net ufs: NOTICE:... (1 Reply)
Discussion started by: SkySmart
1 Replies
10. Solaris
Hi,
Recently from the vmstat output in the image attached, the first line of the cpu idle column shows a value of 15. Although the subsequent values show higher than 90, is there a reason why the first value is so low?
Is this a problem?
Thanks. (4 Replies)
Discussion started by: anaigini45
4 Replies
LEARN ABOUT MOJAVE
init.d
init.d(4) init.d(4)
NAME
init.d - initialization and termination scripts for changing init states
SYNOPSIS
/etc/init.d
/etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appro-
priate to files in the rc?.d directories, where `?' is a single character corresponding to the init state. See init(1M) for definitions of
the states.
The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc-
tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are
incomplete services, and will not be restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d filename>, where S means start this job, K means kill this job, and nn is the
relative sequence number for killing or starting the job.
When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those scripts in /etc/rc[S0-6].d that are prefixed with K followed
by those scripts prefixed with S. When executing each script in one of the /etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a
single argument. It passes the argument 'stop' for scripts prefixed with K and the argument 'start' for scripts prefixed with S. There is
no harm in applying the same sequence number to multiple scripts. In this case the order of execution is deterministic but unspecified.
Guidelines for selecting sequence numbers are provided in README files located in the directory associated with that target state. For
example, /etc/rc[S0-6].d/README. Absence of a README file indicates that there are currently no established guidelines.
Do not put /etc/init.d in your $PATH. Having this directory in your $PATH can cause unexpected behavior. The programs in /etc/init.d are
associated with init state changes and, under normal circumstances, are not intended to be invoked from a command line.
Example 1: Example of /sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The
following steps are performed by /sbin/rc2.
1. In the directory /etc/rc2.d are files used to stop processes that should not be running in state 2. The filenames are prefixed with K.
Each K file in the directory is executed (by /sbin/rc2) in alphanumeric order when the system enters init state 2. See example below.
2. Also in the rc2.d directory are files used to start processes that should be running in state 2. As in Step 1, each S file is executed.
Assume the file /etc/init.d/netdaemon is a script that will initiate networking daemons when given the argument 'start', and will terminate
the daemons if given the argument 'stop'. It is linked to /etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is executed by
/etc/rc2.d/S68netdaemon start when init state 2 is entered and by /etc/rc0.d/K67netdaemon stop when shutting the system down.
svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5)
Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script
mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica-
tions. Existing init.d scripts will, however, continue to be executed according to the rules in this manual page. The details of execution
in relation to managed services are available in svc.startd(1M).
On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other
scripts executed later. This behavior is no longer supported; for altering the environment in which services are run, see the setenv sub-
command in svccfg(1M).
/sbin/rc2 has references to the obsolescent rc.d directory. These references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables. The same is true for the shutdown.d directory.
17 Aug 2005 init.d(4)