1 |
On Thursday 18 March 2010 14:07:37 Renat Golubchyk wrote: |
2 |
> Hi! |
3 |
> |
4 |
> On Wed, 17 Mar 2010 23:19:34 +0000 Mick <michaelkintzios@×××××.com> |
5 |
> |
6 |
> wrote: |
7 |
> > In an aterm I launch top. Then press z c and Shift+W. I get: |
8 |
> > |
9 |
> > Wrote configuration to '/home/michael/.toprc' |
10 |
> > |
11 |
> > Fine I think, Ctrl+c to end it and move on. Next time I fire up top, |
12 |
> > even from the same terminal, it's all looking white with no colour, |
13 |
> > no highlighting, or anything else. Why is this? |
14 |
> |
15 |
> Maybe it will help if you quit from top gracefully by pressing 'q' |
16 |
> instead of killing it by sending a SIGTERM. I suppose top doesn't flush |
17 |
> the write buffer if you just kill it. |
18 |
|
19 |
Thank you all for your responses. Since I installed this amd64 system I have |
20 |
found a couple of 'unexplained' behaviours compared to my x86 systems. This |
21 |
must be one of them. However, some of you also run amd64 and you do not seem |
22 |
to experience the same. This particular problem is rather weird. Why on |
23 |
earth do these four missing keywords are not in my .toprc files? Neither in |
24 |
my root or my plain user accounts. Even more weird is that I added these in |
25 |
both .toprc files and as if by magic my changes in colour etc. showed up when |
26 |
I relaunched top! Now, as soon as I made some more changes and pressed |
27 |
Shift+W the Def, Job, Mem, Usr keywords disappeared again and all changes |
28 |
were no longer visible. |
29 |
|
30 |
What can be causing this? Should I report it as a bug? |
31 |
-- |
32 |
Regards, |
33 |
Mick |