topic Re: parent process kill? in Operating System - HP-UX

parent process kill?

???_185 — Thu, 29 Dec 2005 04:03:28 GMT

I was looking over process didn't using currently.
I just want to know the process have PID=0 must not kiiled, or present in unnecessary process.

Re: parent process kill?

Muthukumar_5 — Thu, 29 Dec 2005 04:08:40 GMT

can you please ellaborate the requirement more? I did not get what you are requiring for?

-Muthu

Re: parent process kill?

Eric Antunes — Thu, 29 Dec 2005 04:09:24 GMT

Hi,

Process with PID=0 is the swapper and you MUST NOT kill it.

Best Regards,

Eric Antunes

Re: parent process kill?

Tvs — Thu, 29 Dec 2005 04:09:37 GMT

Hi,

The pid 0 process is a swapper process. this is the process which is controlling the swapping activity. ( this process controlling two deamon, swapper deamon and vhand deamon)

regards
Tvs

Re: parent process kill?

Arunvijai_4 — Thu, 29 Dec 2005 04:10:36 GMT

Hello,

You shouldn't kill PPID "0" since it is the parent process for all other processes running in HP-UX. It is known as "swapper"

-Arun

Re: parent process kill?

Arunvijai_4 — Thu, 29 Dec 2005 04:13:26 GMT

More information about "swapper"

http://wwwpdp.web.cern.ch/wwwpdp/ose/file/hpux10/UNX1000267.html

PROBLEM TEXT

I do a `ps' and it reports a swapper process. Why is that there, when we
don't swap anymore?

RESOLUTION TEXT

It's correct that the swapper process does not swap entire processes any
more, but it does something similar. When available RAM is very low (below
the "minfree" threshold), the swapper begins deactivating processes. When a
process is targeted for deactivation, that process is removed from the run
queue. Since the process can no longer execute, the pages associated with
the process are less likely to be referenced. The normal paging mechanism
(vhand) will then be more likely to push a deactivated process's pages out
to the "swap" device.

HP considered changing the commands and documentation, but decided against
it. The term "swapper" is deeply ingrained in everyone's minds, and the
swapper still exists even though it no longer does that job by name...

-Arun

Re: parent process kill?

Luk Vandenbussche — Thu, 29 Dec 2005 04:14:19 GMT

Hi,

Don't kill PID 0
I you do this, your server will stop working.
The only solution to solve it will be rebooting your server

Re: parent process kill?

Muthukumar_5 — Thu, 29 Dec 2005 04:24:45 GMT

Is zungwon wanting to kill the process with PID=0?? I think he is trying to some other requiremnet.

-Muthu

Re: parent process kill?

Sivakumar TS — Thu, 29 Dec 2005 08:22:43 GMT

Hi,

PID 0 is the mother of ALL process. Please DONT kill that.

Also whenever you kill any process which has already forked some chiled process you should take CARE ! because those chils process of would enter ZOOMBIE state and you may have to kill all of them manually.

go thro the man page of "ps" for more info.

With Regards,

Siva.

Re: parent process kill?

???_185 — Fri, 30 Dec 2005 02:13:25 GMT

I just have examine root's process.
root 10 0 0 Sep 24 ? 0:09 autofskd
root 18 0 0 Sep 24 ? 360:52 ksyncer_daemon
root 21 0 0 Sep 24 ? 0:00 pagetable_init_daemon ??
root 22 0 0 Sep 24 ? 0:00 supsched
root 23 0 0 Sep 24 ? 0:00 strmem = ""
root 24 0 0 Sep 24 ? 0:00 strweld =
root 25 0 0 Sep 24 ? 0:00 strfreebd
root 3 0 0 Sep 24 ? 53:47 statdaemon ->
root 4 0 0 Sep 24 ? 4:19 unhashdaemon ->
root 26 0 0 Sep 24 ? 6:22 progressdaemon
root 27 0 0 Sep 24 ? 0:00 awd
root 28 0 0 Sep 24 ? 0:00 kmemdaemon
root 29 0 0 Sep 24 ? 0:00 ttisr
root 30 0 0 Sep 24 ? 0:41 ipmid
root 37 0 0 Sep 24 ? 0:00 eventdaemon
root 38 0 0 Sep 24 ? 699:01 schedcpu
root 39 0 0 Sep 24 ? 1119:28 pagezerod
root 40 0 0 Sep 24 ? 41:59 cmcd
root 59 0 0 Sep 24 ? 0:00 kend
root 87 0 0 Sep 24 ? 0:00 rng
root 649 1 0 Sep 24 ? 0:00 /usr/sbin/ptydaemon
root 664 1 0 Sep 24 ? 0:00 /usr/sbin/hotplugd /var/adm/hotplugd.log trunc
root 678 1 0 Sep 24 ? 0:00 /usr/lbin/nktl_daemon 0 0 0 0 0 1 -2
root 1726 1 0 Sep 24 ? 14:43 /opt/dce/sbin/rpcd
root 1739 1736 0 Sep 24 ? 0:00 /opt/wbem/sbin/cimservera
root 1792 1 3 Sep 24 ? 427:10 /usr/sbin/pwgrd
root 2178 1 0 Sep 24 ? 0:04 /sbin/krsd -i
root 2052 1 0 Sep 24 ? 18:45 vxsvc -r /opt/VRTSob/config/Registry -e
root 2164 1 0 Sep 24 ? 0:00 /sbin/sh /usr/dt/bin/dtrc
root 2124 2122 0 Sep 24 ? 0:00 llbserver
root 2221 2164 0 Sep 24 ? 0:00 /usr/dt/bin/dtlogin
root 2180 1 0 Sep 24 ? 1:59 /opt/wbem/sbin/cimserverd
root 2179 1 0 Sep 24 ? 0:00 /sbin/sfd
root 2200 1 0 Sep 24 ? 88:20 /usr/lbin/kcmond
root 2375 1826 0 Sep 24 ? 67:10 psmctd->EMS Hardware Monitors
root 3580 3577 3 Sep 24 ? 471:51 /usr/lbin/cmgmsd
root 3593 0 0 Sep 24 ? 0:00 resyncd
root 1644 1 0 Sep 24 ? 0:00 /usr/sbin/hp_unixagt
root 1830 1 0 Sep 24 ? 0:00 /usr/sbin/envd
root 771 1 0 Sep 24 ? 0:45 /usr/lbin/ilmid
root 1291 1 0 Sep 24 ? 0:05 /usr/sbin/rpcbind -> nfs.core
root 1653 1 0 Sep 24 ? 27:45 /usr/sbin/ipv6agt
root 1711 1 0 Sep 24 ? 0:00 /usr/sbin/fddi4subagt
root 1736 1 0 Sep 24 ? 141:27 /opt/wbem/sbin/cimserver

is there processes have to erase? especially, I couldn't know how can I erase fddi4subagt?

Re: parent process kill?

Joseph Loo — Fri, 30 Dec 2005 02:31:48 GMT

hi,

fddi4subagt is an snmp agent. u may stop it by:

# /sbin/init.d/SnmpFddi4 stop

# ps -ef|grep -i fddi4
to verify if the process is stop.

regards.