[ale] something is eating my cpu?!

[J.M. Taylor]

Well, top *could* be fubar'd and eating up cycles. VI does that to me
sometimes if I accidentally close the terminal window before doing :wq.

You can 'ps -ef |more ' or 'ps -ef |grep top' to see if top is in fact
going nutzoid even after you've quit from it.

If the reboot cleared it up, it was probably just a hung process...in the
future, using the ps -ef |more (or ps ax |more depending on your
preferences) to find the evil process and then killing just that process
number is a much happier way of regaining your machine than
rebooting...rebooting takes too long.

If the reboot didn't clear it up, I'd suggest lsof to see what's really
running on your machine.  Someone else on ALE I'm sure can be more helpful
about the proper uses of lsof, I usually only use it to see processes are
binding to what ports.

Good luck
jenn

Sean Kilpatrick said:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I could use a little help.
> Running RH 9.0; Something has suddenly started eating up my
> CPU cycles. But when I run top, this is what I see, which makes
> no sense at all:
>
> - ---------------------- <begin copied material>
> -----------------------------
>
> 23:04:02  up 2 days,  6:59,  4 users,  load average: 1.11, 1.41, 1.67 78
> processes: 73 sleeping, 5 running, 0 zombie, 0 stopped
> CPU states:  50.8% user  49.1% system   0.0% nice   0.0% iowait   0.0%
> idle Mem:   513608k av,  457268k used,   56340k free,       0k shrd,
> 124900k  buff
>                     356884k actv,   10160k in_d,    7088k in_c
> Swap: 1060208k av,    5308k used, 1054900k free                  195096k
>  cached
>
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU
> COMMAND
>  4771 root      25   0  1044 1044   804 R    95.4  0.2 308:08   0 top
> 5405 kilpatms  15   0 19956  19M 13164 S     1.7  3.8   4:02   0
> kdeinit 5276 root      15   0  276M  20M  4156 S     1.3  4.0   0:16
> 0 X 5391 kilpatms  15   0  5508 5508  4164 R     1.1  1.0   3:03   0
> artsd
>
> - ---------------------------- <end copied material>
> -------------------------
>
> It would seem obvious that top is NOT eating up 95% of the CPU cycles.
>
> But I have no idea how to even begin trying to figure out what is really
> going on.
>
> I am going to shut down and reboot and see if that clears things up, but
> I really would like to discover what is going on here.
>
> Sean
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+/QZn73hVp4UeGJERAn2dAJ48qphvuRsLH8TupSVqY5lVvGAzOwCgtLIz
> yce/zGsKr3wWOSx5eNtXClM=OguH
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale



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