Apparently in 2.6.x kernels top does not look at the threads of programs.
So if say you have the daemon program 'foo' running, which has spawned a
few threads which are using 100% of the processor juice, top will show the
processor usage at 100% but will show foo as using 0% of the processor.

The problem is that the base install of FC2 has a few things running in cron
(I assume) which are doing just that. They're sucking up all my proccessor
power, but I can't run top to find out what it is that's running so that I
can either keep it from running entirely, or re-schedule to a more
convenient time.

Does anybody know of a way to find out what processes are doing this since
top does not appear to do the trick?

TIA,
Joseph

Joseph wrote:

> Apparently in 2.6.x kernels top does not look at the threads of programs.
> So if say you have the daemon program 'foo' running, which has spawned a
> few threads which are using 100% of the processor juice, top will show the
> processor usage at 100% but will show foo as using 0% of the processor.
>
> The problem is that the base install of FC2 has a few things running in
> cron
> (I assume) which are doing just that. They're sucking up all my
> proccessor power, but I can't run top to find out what it is that's
> running so that I can either keep it from running entirely, or re-schedule
> to a more convenient time.
>
> Does anybody know of a way to find out what processes are doing this since
> top does not appear to do the trick?
>
> TIA,
> Joseph

Read the man page for 'ps'.

ps -xau

Hey thanks. I didn't know that ps could show CPU usage statistics.
Apparently you can get it to show the threads too. This is exactly what I
was looking for.

Thanks again,
Joseph

>
> Read the man page for 'ps'.
>
> ps -xau

Joseph wrote:

> Hey thanks. I didn't know that ps could show CPU usage statistics.
> Apparently you can get it to show the threads too. This is exactly what I
> was looking for.
>
> Thanks again,
> Joseph
>
>>
>> Read the man page for 'ps'.
>>
>> ps -xau

I occasionally like to use the /bin/ps version of
ps, then you can request particular columns
(like the process owner, process id, % of cpu and
the command line arguments)

/bin/ps -A -o user,pid,pcpu,args

which shows something like:
root 2675 0.0 /sbin/mingetty tty5
root 2676 0.0 /sbin/mingetty tty6
mos 2827 0.0 -tcsh
mos 2854 0.0 /bin/sh /usr/X11R6/bin/startx
mos 2866 0.0 xinit /etc/X11/xinit/xinitrc --
root 2867 0.0 X :0
mos 2906 0.0 /bin/sh /usr/bin/startkde
mos 2920 0.0 ssh-agent /home/mos/.Xclients
mos 2960 0.0 kdeinit: Running...

since there's fewer columns this way, you get to
see more of the args (not chopped off on the right edge)

Mark

On Thursday 09 December 2004 22:32 Gumby (none@xxxyy.com) wrote to
comp.os.linux.setup as msd_id: <cN8ud.3613$mn6.2661@trnddc07> :

> Joseph wrote:
>
>> Hey thanks. I didn't know that ps could show CPU usage statistics.
>> Apparently you can get it to show the threads too. This is exactly what
>> I was looking for.
>>
>> Thanks again,
>> Joseph
>>
>>>
>>> Read the man page for 'ps'.
>>>
>>> ps -xau
>
> I occasionally like to use the /bin/ps version of
> ps, then you can request particular columns
> (like the process owner, process id, % of cpu and
> the command line arguments)
>
> /bin/ps -A -o user,pid,pcpu,args
>
> which shows something like:
> root 2675 0.0 /sbin/mingetty tty5
> root 2676 0.0 /sbin/mingetty tty6
> mos 2827 0.0 -tcsh
> mos 2854 0.0 /bin/sh /usr/X11R6/bin/startx
> mos 2866 0.0 xinit /etc/X11/xinit/xinitrc --
> root 2867 0.0 X :0
> mos 2906 0.0 /bin/sh /usr/bin/startkde
> mos 2920 0.0 ssh-agent /home/mos/.Xclients
> mos 2960 0.0 kdeinit: Running...
>
> since there's fewer columns this way, you get to
> see more of the args (not chopped off on the right edge)
>
> Mark

You can see all of the args if you pipe output of 'ps' to 'more' or 'less'
eg: ps xau | less

it won't truncate, but it will line wrap.

dxp