You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "VanderHart, Robert" <Ro...@umassmed.edu> on 2002/06/05 17:41:33 UTC

When do processes need to be killed?

I'm a relative newbie on Apache.  We're running Linux 7/Apache 1.3.12.
Lately I've noticed there's a process (see below) called CANamingAdapter
that seems to keep running up CPU time.  The process itself is a ColdFusion
server process that controls the data store for application management
features.

I've killed the process using kill -9, but it immediately comes back under a
different PID and then keeps running up time.  It's not taking up much %CPU
or %MEM, so I'm not certain how to interpret the high number under TIME.

It seems most of the documentation I've read discusses how to kill
processes, but not if/when they should be killed.  Any
suggestions/help/direction would be most appreciated.

(I apologize if the table below doesn't render correctly on your screen; it
is best viewed as plain text).

____________________________________________________________________________
____
163 processes: 162 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:  8.5% user,  2.9% system,  0.0% nice, 88.4% idle
Mem:   127696K av,  122728K used,    4968K free,   49012K shrd,   38464K
buff
Swap:   72252K av,   32712K used,   39540K free                   32768K
cached

  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 9067 nobody    13   0 21168  16M  6824 S     6.8 13.2   1:39 cfserver
 9276 rvanderh   8   0  1128 1128   812 R     2.3  0.8   0:00 top
23565 root       3   0  1300  800   460 S     1.1  0.6  78:21
CANamingAdapter
 1125 nobody     3   0 16692  10M   176 S     0.9  8.2  13:11 java
 8999 apache     1   0  5180 2652  2320 S     0.1  2.0   0:00 httpd
    1 root       0   0   120   72    48 S     0.0  0.0   0:06 init
    2 root       0   0     0    0     0 SW    0.0  0.0   0:08 kflushd
    3 root       0   0     0    0     0 SW    0.0  0.0   0:09 kupdate
    4 root       0   0     0    0     0 SW    0.0  0.0   0:00 kpiod
    5 root       0   0     0    0     0 SW    0.0  0.0   1:36 kswapd
    6 root     -20 -20     0    0     0 SW<   0.0  0.0   0:00 mdrecoveryd
   61 root       0   0     0    0     0 SW    0.0  0.0   0:00 khubd
  372 root       0   0   220  168   120 S     0.0  0.1   0:00 syslogd
  382 root       0   0   496  184   156 S     0.0  0.1   0:00 klogd
  397 rpc        0   0    88    0     0 SW    0.0  0.0   0:00 portmap
  413 root       0   0     0    0     0 SW    0.0  0.0   0:00 lockd
  414 root       0   0     0    0     0 SW    0.0  0.0   0:00 rpciod
  424 rpcuser    0   0   120    0     0 SW    0.0  0.0   0:00 rpc.statd
  439 root       0   0    64    0     0 SW    0.0  0.0   0:00 apmd
  490 root       0   0   128   48    28 S     0.0  0.0   0:00 automount
  543 nobody     0   0   128   24    16 S     0.0  0.0   0:00 identd
____________________________________________________________________________
___



Robert J. Vander Hart
Electronic Resources Librarian
The Lamar Soutter Library
University of Massachusetts Medical School
55 Lake Avenue N
Worcester  MA  01655

Voice: (508) 856-3290
Fax: (508) 856-5899
Email: Robert.VanderHart@umassmed.edu
Web: http://library.umassmed.edu 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: When do processes need to be killed?

Posted by Lee Fellows <lf...@4lane.com>.
  As a general rule, iff they are interferring with the normal running
  of the system.  Time, by itself, is meaningless.  



On Wed, 2002-06-05 at 11:41, VanderHart, Robert wrote:
> I'm a relative newbie on Apache.  We're running Linux 7/Apache 1.3.12.
> Lately I've noticed there's a process (see below) called CANamingAdapter
> that seems to keep running up CPU time.  The process itself is a ColdFusion
> server process that controls the data store for application management
> features.
> 
> I've killed the process using kill -9, but it immediately comes back under a
> different PID and then keeps running up time.  It's not taking up much %CPU
> or %MEM, so I'm not certain how to interpret the high number under TIME.
> 
> It seems most of the documentation I've read discusses how to kill
> processes, but not if/when they should be killed.  Any
> suggestions/help/direction would be most appreciated.
> 
> (I apologize if the table below doesn't render correctly on your screen; it
> is best viewed as plain text).
> 
> ____________________________________________________________________________
> ____
> 163 processes: 162 sleeping, 1 running, 0 zombie, 0 stopped
> CPU states:  8.5% user,  2.9% system,  0.0% nice, 88.4% idle
> Mem:   127696K av,  122728K used,    4968K free,   49012K shrd,   38464K
> buff
> Swap:   72252K av,   32712K used,   39540K free                   32768K
> cached
> 
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>  9067 nobody    13   0 21168  16M  6824 S     6.8 13.2   1:39 cfserver
>  9276 rvanderh   8   0  1128 1128   812 R     2.3  0.8   0:00 top
> 23565 root       3   0  1300  800   460 S     1.1  0.6  78:21
> CANamingAdapter
>  1125 nobody     3   0 16692  10M   176 S     0.9  8.2  13:11 java
>  8999 apache     1   0  5180 2652  2320 S     0.1  2.0   0:00 httpd
>     1 root       0   0   120   72    48 S     0.0  0.0   0:06 init
>     2 root       0   0     0    0     0 SW    0.0  0.0   0:08 kflushd
>     3 root       0   0     0    0     0 SW    0.0  0.0   0:09 kupdate
>     4 root       0   0     0    0     0 SW    0.0  0.0   0:00 kpiod
>     5 root       0   0     0    0     0 SW    0.0  0.0   1:36 kswapd
>     6 root     -20 -20     0    0     0 SW<   0.0  0.0   0:00 mdrecoveryd
>    61 root       0   0     0    0     0 SW    0.0  0.0   0:00 khubd
>   372 root       0   0   220  168   120 S     0.0  0.1   0:00 syslogd
>   382 root       0   0   496  184   156 S     0.0  0.1   0:00 klogd
>   397 rpc        0   0    88    0     0 SW    0.0  0.0   0:00 portmap
>   413 root       0   0     0    0     0 SW    0.0  0.0   0:00 lockd
>   414 root       0   0     0    0     0 SW    0.0  0.0   0:00 rpciod
>   424 rpcuser    0   0   120    0     0 SW    0.0  0.0   0:00 rpc.statd
>   439 root       0   0    64    0     0 SW    0.0  0.0   0:00 apmd
>   490 root       0   0   128   48    28 S     0.0  0.0   0:00 automount
>   543 nobody     0   0   128   24    16 S     0.0  0.0   0:00 identd
> ____________________________________________________________________________
> ___
> 
> 
> 
> Robert J. Vander Hart
> Electronic Resources Librarian
> The Lamar Soutter Library
> University of Massachusetts Medical School
> 55 Lake Avenue N
> Worcester  MA  01655
> 
> Voice: (508) 856-3290
> Fax: (508) 856-5899
> Email: Robert.VanderHart@umassmed.edu
> Web: http://library.umassmed.edu 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: When do processes need to be killed?

Posted by Pietro Cagnoni <pc...@mclink.net>.
it's a little offtopic...

VanderHart, Robert wrote:
> I'm a relative newbie on Apache.  We're running Linux 7/Apache 1.3.12.
> Lately I've noticed there's a process (see below) called CANamingAdapter
> that seems to keep running up CPU time.  The process itself is a ColdFusion
> server process that controls the data store for application management
> features.

if you use ColdFusion, maybe you need it running!

  > I've killed the process using kill -9, but it immediately comes 
back under a
> different PID and then keeps running up time.  It's not taking up much %CPU
> or %MEM, so I'm not certain how to interpret the high number under TIME.

the TIME column is the cpu time the process used since it started.
from what i see in your top output, it's a very little load: keep
it active (ie don't kill it) if it doesn't cause you problems.

since it looks like you're new to unix in general (my apologies if
you're not) remember that kill -9 doesn't allow the killed process
to terminate properly, so use it just if you absolutely need it.

hope it helps.

pietro.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org