Please monitor my system

[Gyro]

How do I install a system monitor on DSL?
I have seen DamnSmallLinux installations which have a system monitor in the top right corner of the screen.  However in my DSL-2024 installation it's not there. 
Thank you.

[grindstone]

You mean conky? I think (?) the only time one does *not* have that is when choosing lessram or loweram maybe (forgot). Or do you mean another separate utility. What happens if you type

conky &

Alternatively, can you find a link to what it is that you want displayed (and a screenie of what you have)?

Thanks.

[Gyro]

Thanks. I probably mean Conky but it isn't enabled on my system.

[grindstone]

OK, I've just verified that conky starts for all options except "lower ram" (aka lessram on boot options).

   

   

Please help us understand what you are running and how you are starting it.

What boot options are you choosing? 

If you are choosing lower ram, you will have to start it by hand until we prove that it works (unless you are always live sessions w/o installation anywhere).  Open a terminal, type the command to start it and note mentally the process number to use in a second command so you can close the terminal later w/o terminating the conky process. 

   

   

If it doesn't start when you type

Code:

conky &

tell us what it said.

[Gyro]

Thank you.
When I run "conky &" from terminal the Conky screen doesn't come up, but it says this (I didn't manage to take a screen shot):

$ conky &
[1] 2752
system@prompt:~
$ Conky: forked to background, pid is 2753

Conky: desktop window (15f) is root window
Conkdy: window type - normal
Conky: drawing to created window (0x2000001)
Conky: drawing to double buffer

I'm using a full installtion, as far as I'm aware without the "lowram" boot option.

[grindstone]

Thanks. OK it's running but not in the top layer. Probably have two of them, now. If it's the same session, kill those (or just reboot). If you have to kill them, one way is like this:

Code:

pidof conky

< note the process numbers >

Code:

kill -9 <process numbers space-delimited>

Before we change anything, do this:

Menu -> Desktop -> Conky On/Off

Try that twice--does it show on the second try? I've had it display the second time but not the first (maybe it was AntiX) but might've been a JWM vs. Fluxbox thing. BTW, which are you running?

If that didn't work, your answer might be here.

[Gyro]

Hi and thanks for your help, Grindstone. I'm running Fluxbox. Sometimes JWM for fun.
When I just started Fluxbox and searched for the process ID of Conky, none was found.
Then I hit Desktop>Conky On/Off repeatedly, but it didn't appear.
After I restarted, Conky was on; I killed it and hit Desktop>Conky On/Off repeatedly, again to no avail.
When I run the command conky from my terminal (called urxvt) it replies:

Code:

Conky: forked to background, PID is 1999
(System prompt)
Conky: desktop window (15f) is root window
Conky: window type - normal
Conky: drawing to created window (0x1400001)
Conky: drawing to double buffer

[grindstone]

Having trouble recreating this but found much variable behavior on different systems. I think you have to play with the .conkyrc file, start, kill, re-try, etc.

My best guess is you change own_window normal to own_window desktop

Between that, double_buffering, transparent, and background, one can make many things happen. Sometimes a black background but it runs (until one clicks the mouse on the desktop which crashes it, etc.).