[ale] kdeinit

Michael D. Hirsch mhirsch at nubridges.com
Tue Jan 28 12:19:22 EST 2003


On Monday 27 January 2003 10:26 pm, cfowler wrote:
> WTF?
>
>  10:33pm  up 4 days,  1:32,  8 users,  load average: 1.49, 1.40, 1.30
> 87 processes: 81 sleeping, 6 running, 0 zombie, 0 stopped
> CPU states:  3.3% user,  5.3% system, 91.2% nice,  0.0% idle
> Mem:   223944K av,  219472K used,    4472K free,       0K shrd,    1680K
> buff Swap:  396128K av,  200100K used,  196028K free                  
> 22900K cached
>
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>  2216 cfowler    9   0  126M  56M 18728 R     0.0 25.9  10:45 kdeinit
>  2639 cfowler    9   0 69500  47M 27764 S     0.3 21.8  11:20 kdeinit
>  2039 root       9   0 72368  26M  3292 R     6.1 12.2  44:50 X
>  2593 cfowler    9   0 20824  18M 10588 R     0.0  8.5   3:07 kdeinit
>  6621 cfowler    9   0 29240  17M 12952 S     0.0  7.9   1:03 kdeinit
>
> My system always behaves odly at times.  I run KDE under RH 7.3 with the
> lates updates.  Sometimes I have to use atl-tab to cycle through the
> programs because the toolbar at the bottom fails to respond to mouse
> clicks.  Why does kdeinit use so much memory?  The size is 126M?  Maybe
> a leak or is that wahy you C++/Java folks call progress :)

You may (not) be aware that kdeinit can be just about any kde program--and 
I don't know a good way of distinguishing them.  To speed up application 
start-up time, the kicker essentially starts each appliacation by a kind 
of fork/exec rather than running a new process.  I don't understand all 
the details, but the end result is that all processes started like that 
are named "kdeinit".  It does look like you have a couple of runaway 
processes.  You might try killing them and see if something important 
dies.

Michael
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale






More information about the Ale mailing list