1 |
Yohan Pereira wrote: |
2 |
> On 11/11/13 at 01:44am, Dale wrote: |
3 |
>> Yohan Pereira wrote: |
4 |
>>> On 10/11/13 at 08:07pm, Walter Dnes wrote: |
5 |
>>>> [i660][waltdnes][~] ps -ef | grep firefox |
6 |
>>>> waltdnes 28696 11663 2 19:35 pts/22 00:00:07 firefox |
7 |
>>>> waltdnes 28836 28825 0 19:39 pts/30 00:00:00 grep --color=auto firefox |
8 |
>>>> |
9 |
>>>> Only one Firefox process exists. (I can't seem to prevent the grep |
10 |
>>>> command from listing itself). |
11 |
>>> Try this hack :) |
12 |
>>> |
13 |
>>> $ ps -ef | grep [u]rxvt |
14 |
>>> yohan 3559 1 0 11:50 ? 00:00:00 urxvt |
15 |
>>> yohan 3667 1 0 11:52 ? 00:00:00 urxvt |
16 |
>>> |
17 |
>> That one didn't return anything. I got plenty of output without the |
18 |
>> grep tho. Sort of close to what I usually get with ps aux. |
19 |
>> |
20 |
>> Dale |
21 |
> |
22 |
> I'm sorry, that was a hack to prevent grep from listing it self in the |
23 |
> ps out-put, nothing to do with your problem specifically, should've made |
24 |
> that clear :). |
25 |
> |
26 |
|
27 |
|
28 |
Oh OK. That doesn't bother me. I just ignore it. Heck, it's a process |
29 |
just like anything else. LOL |
30 |
|
31 |
My next plan, I'm going to create three thingys on my desktop. One for |
32 |
each session. I'm hoping that the session will be listed in the command |
33 |
so that at least I know which is which in the ps list. I just got to |
34 |
google up the proper command. |
35 |
|
36 |
Thanks for the help tho. Right now, I'm doing a emerge -e system and |
37 |
plan to start a emerge -e world when I leave in the AM to take my bro to |
38 |
the Doctor. It may not help one dang bit but what the heck. I need to |
39 |
break in this new CPU/cooler grease anyway. ;-) |
40 |
|
41 |
Dale |
42 |
|
43 |
:-) :-) |
44 |
|
45 |
-- |
46 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |