hi <br><br><div><span class="gmail_quote">On 9/25/07, <b class="gmail_sendername">Bill Kendrick</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Sep 25, 2007 at 01:29:35PM -0700, Christian Einfeldt wrote:<br>> There are also some graphical user programs that will show you the system<br>> usage. It varies from distro to distro. Which distro are you using?
<br><br>ksysguard under KDE (e.g., on Kubuntu) is a pretty nice graphical 'top'.<br>You can filter, see processes as a tree (child/parent relationships, etc.).</blockquote><div><br>+1 I recently wrote some newbie documentation in using KSysGuard because I was using it to try to figure out the Edgy Kubuntu problem that I am having on one of my boxes that I am using for rendering the Digital Tipping Point film (that problem is kind of gnarly in itself, and I am going to post about it soon). In the process of trying to figure out why my hd light stays on under Edgy Kubuntu, but not under openSUSE
10.2 on the same box, I had to figure out whether there was a bad driver under Edgy for my hd light, or whether my hd was actually being read / written continuously as the light indicated. It turns out that ksysguard was able to tell me that yes, in fact, I am having that problem with my hd. I learned a little bit in the process, and so put up a description of what I learned here. Please feel free to edit it, because I am, after all, a relative newbie, and prone to doing things the hard way:
<br><br><a href="http://en.opensuse.org/Monitor_your_hard_disk_activity_with_KSysGuard">http://en.opensuse.org/Monitor_your_hard_disk_activity_with_KSysGuard</a><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, from the command line, instead of:<br><br> ps aux | grep foo<br> [figure out foo's pid]<br> kill pid<br><br>you can often just do:<br><br> killall foo</blockquote><div><br>This is really nice, and it worked with killing
OpenOffice.org by doing<br><br>$ killall soffice<br><br>But I did not have similar success in my attempt to kill Firefox with <br><br>$ killall firefox<br><br>Instead of killing Firefox, it just returned me to a user prompt:
<br><br>19:53 linux-athlon64x2:~ > killall soffice<br>19:53 linux-athlon64x2:~ > killall firefox<br>19:53 linux-athlon64x2:~ ><br><br>What do you suppose I was doing wrong there? Thanks in advance.</div></div><br>