05-03-2011
I'm coming back with my problem.
Quote:
root@gen1445/home/root> ps -ef|grep defunct
root 66686 14450 1 0:00 <defunct>
root 77106 14450 0 0:00 <defunct>
root@gen1445/home/root> ps -ef|grep 14450
root 14450 8046 0 14:52:52 - 0:00 /usr/dt/bin/dtlogin
root 66686 14450 1 0:00 <defunct>
root 77106 14450 0 0:00 <defunct>
root 98148 51824 0 14:56:00 pts/5 0:00 grep 14450
root@gen1445/home/root> /usr/bin/stopsrc -s dtsrc; sleep 3 ; /usr/bin/startsrc -s dtsrc (stop/start of dtlogin)
0513-044 L'arrêt du sous-système dtsrc a été demandé.
0513-059 Le sous-système dtsrc a été démarré. PID du sous-système : 48426.
root@gen1445/home/root> ps -ef|grep defunct
root@gen1445/home/root> date
mar 3 mai 14:58:11 DFT 2011
root@gen1445/home/root> ps -ef|grep defunct
root 47870 51824 0 14:58:17 pts/5 0:00 grep defunct
root@gen1445/home/root> ps -ef|grep defunct
root 63560 51824 0 14:58:26 pts/5 0:00 grep defunct
root@gen1445/home/root> ps -ef|grep defunct
root 102110 48426 1 0:00 <defunct>
root@gen1445/home/root> ps -ef|grep defunct
root 62554 51824 0 14:58:49 pts/5 0:00 grep defunct
root 102110 48426 1 0:00 <defunct>
root@gen1445/home/root> ps -ef|grep defunct
root 45718 51824 0 14:59:06 pts/5 0:00 grep defunct
root 79850 48426 0 0:00 <defunct>
root 102110 48426 1 0:00 <defunct>
root@gen1445/home/root> ps -ef|grep 48426
root 48426 8046 0 14:57:50 - 0:00 /usr/dt/bin/dtlogin
root 79850 48426 0 0:00 <defunct>
root 102110 48426 1 0:00 <defunct>
stopsrc and startsrc, stop the defunct process but after a while (one minute) some other defunct process are coming back.
Do you have any ideas why they come back?
10 More Discussions You Might Find Interesting
1. SCO
Hello ,
I've got 2 defunct processes due to scohttp process :
# ps -ef | grep 460
root 460 1 0 Sep-21 ?
00:00:00 /var/scohttp/scohttpd -d /var/scohttp
root 15399 15228 2 09:06:23 ttyp1 00:00:00 grep 460
nouser 14600 460 0 - - 00:00:00... (0 Replies)
Discussion started by: npn35
0 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. UNIX for Advanced & Expert Users
Hi unix lovers,
i have question about defunt process on HP-UX. Are there any side-effects of defunct process?
Can a parent process get killed because there are lot of defunct processes? say 50 defunct childs??
-Ashish (1 Reply)
Discussion started by: shriashishpatil
1 Replies
4. Programming
Hi!
I'm newbi in the Unix. I've a C++ Program from where one shell gets executed. Sample C++ code is --
transactionID = 1199;
case 1199:
//*************************************************
// Received the suspend signal.... (2 Replies)
Discussion started by: satyakide
2 Replies
5. Solaris
Hello out there!
I'm using dtlogin with my SunRay 2 and SunRay Server Software 4.0.
Now I want to customize the look an funcionality of the dtlogin. e.g. disable the Options - Button or change the Helptext.
Can anybody give me a hint where to find a good manual for dtlogin or which files I... (2 Replies)
Discussion started by: Blang
2 Replies
6. Solaris
My system is running solaris zones and oracle dbs in all the zones .. and now i find more then 4500 defunct processes in ps output. Can anyone know about this how to kill these
# ps -ef | grep defunct | wc -l
4899
And when i do ptree on one of the pid it shows most of the defunct... (3 Replies)
Discussion started by: fugitive
3 Replies
7. Programming
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <string.h>
#include <sys/wait.h>
#include <sys/types.h>
#include <stdint.h>
#define LINE_MAX 80
int main()
{
pid_t pid, pid1;
char line;
char *lines;
char *key, *data,... (2 Replies)
Discussion started by: p00ndawg
2 Replies
8. UNIX for Dummies Questions & Answers
All,
I am getting a wired scenario, Not all times but some times i am getting the defunct process for a program. If i rerun the same program it is working fine.This defunct scenario is not occuring often. And this is happening only for the one program in my system that to sometimes
Can you... (1 Reply)
Discussion started by: arunkumar_mca
1 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. Solaris
Hi everyone,
I'm working on continous integration with Jenkins.
I’m facing an issue while connecting a slave (solaris sparc 8) with Jenkins ver. 1.532.2
This slave is connected via the option “Launch slave via execution of command on the Master”.
Connection is established with:
-... (1 Reply)
Discussion started by: javaPIC
1 Replies
chroot(8) System Manager's Manual chroot(8)
NAME
chroot - Changes the root directory of a command
SYNOPSIS
/usr/sbin/chroot directory command
DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command
executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated
by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in
effect, directory is relative to the current root of the running process.
Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file
system and the relevant pathnames for the files map correctly in the new root file system.
For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and
/etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the
output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on
description files produced by the ctab command may also fail if the required description files are not present in the new root file system.
The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe-
cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring
use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new
root file system in the appropriate locations.
EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is
on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec-
ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root
file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must
contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among
others) on the new root file system.
Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and
return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and
the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command
similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a:
chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out
The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c
file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial
root file system. To create a file relative to the original root rather than the new one, use this syntax and enter:
chroot directory command > file
CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite
the file system.
FILES
Specifies the command path.
RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1)
Functions: chdir(2), chroot(2) exec(2) delim off
chroot(8)