solved
solved
Last edited by bosele; January 14th, 2008 at 06:02 PM. Reason: found it
Yea, yea, I know ... {wipping off my nose from where you rubbed it}
But I like to learn and play with things. It's easy enough to edit out.
I keep telling everyone I'm not a programmer BUT:
1. at one time a friend referred to me openly on the local BBS's as "The Batch File King". I had a couple I wrote for people that came in close to 250k. And my computer ( a 486 at that time running DOS 6.6 was virtually batch file driven, complete with a Wildcat 3 node BBS (yup, three 14.4k modems) running with QEMM.
2. I "edited" AutoCad v9 (DOS) Lisp files to include a lot of AutoCad 10 functions, and
3. I "wrote" a lisp file (AutoCad v9) to automate drawings from "land survey" notes. Such as cut and fill for road construction, building foundations and general land contours. It included everything, elevations, angles (to 100th of a second), distances.
But mostly it involves looking at something ... seeing how it works and playing with it. #2 took one evening (I should say until the wee hours of the AM) at home on my old XT, they had 386's at work. Doing #2 gave me the insight and the will to try #3, it took me a couple of weeks knowing nothing about lisp, other than what I had learned doing #2, and NO formal training.
Bruce
We have something in common. At one time, years ago, I wrote an entire add-on menu system for AutoCAD r10 for the enginnering firm I used to work for. It would insert mechanical symbols and outlets and you name it. Also put the object snaps on the function keys. Heavy use of AutoLISP.
Yeah, I took out the single execi call I had in mine for rhythmbox; it was set to update every 10 seconds (maybe every 5?) so as to get an accurate readout of the song information.
I didn't feel justified in it because I could just as easily open rhythmbox and see the info, and then I switched to exaile entirely.
ninja edit as for batch files; those are some of the most fun to write. I write tons of them for my work all the time. My personal favorite is a batch file to command-line defrag that dumps its output into a logfile within a directory; we set that one on a monthly scheduled job (Win2003R2)
The views expressed in this post belong to Tristam Green and do not represent the views of any other entity, foreign or domestic, as long as you both shall live, Amen.
OMG! Cheesecake! | Fuduntu - catch the fever!
Lets correct some stuff on your conkyrc first regarding configuration
-The font located in the line:
xftfont EunjinNakseoixelsize=12
is first of all... non existant! I googled it and there is no such font! Instead use something simple like Dejavu Sans and seperate the font name from the size using " : " . So
xftfont Dejavu Sans:size=12
You change the font to your preference. The way it is now makes conky use its default font.
- The position and the gaps! They are located here
gap_x 830
gap_y 50
alignment top_left
This bit tells conky to start drawing from the top-left corner of the screen, then leave a HUGE 830 pixel gap from the left side and a 50 pixel gap from the top! This makes your conky stand somewhare in the 3/4 ofyour desktop! Instead i suggest this
gap_x 0
gap_y 0
alignment top_right
This makes conky start drawing from the top-right corner and leave NO gaps.
- The fact that conky stays on top of lies here I think
own_window_type override
Change it to
own_window_type normal
and see what happens.
Now lets correct its other appearence problems
- The drive temperature can also be retrieved this way
${execi 5 hddtemp /dev/hda}
I know it looks ugly but with some grep usage, you can make it look good.
I have no idea about that FSB line, what is it?
- The gaps between each line make your conky use a lot of space!
Remove the empty lines and, if possible, make the signs a bit smaller like... 16-20 size max.
I dont use email and weather script, so I cant say something about them. Please post them if you like
Trying to get conky to see my temperatures:
bruloo@The-Team:~$ sensors
adm1025-i2c-2-2d
Adapter: SMBus I801 adapter at efa0
+2.5V: +2.47 V (min = +0.00 V, max = +3.32 V)
VCore: +1.65 V (min = +0.00 V, max = +2.99 V)
+3.3V: +3.35 V (min = +0.00 V, max = +4.38 V)
+5V: +5.05 V (min = +0.00 V, max = +6.64 V)
+12V: +12.19 V (min = +0.00 V, max = +15.94 V)
VCC: +3.21 V (min = +0.00 V, max = +4.38 V)
CPU Temp: +47.0°C (low = +0°C, high = +127°C)
M/B Temp: +39.0°C (low = +0°C, high = +127°C)
vid: +1.650 V (VRM Version 8.2)
smsc47m1-isa-0800
Adapter: ISA adapter
fan1: 0 RPM (min = 5120 RPM, div = 1)
fan2: 0 RPM (min = 5120 RPM, div = 1)
bruloo@The-Team:~$
I added the line:
CPU Temp: ${execi 6 /usr/bin/sensors | grep CPU Temp | paste -s | cut -c12-19}
All I see in conky is:
CPU Temp:
The error:
bruloo@The-Team:~$ ./.startconky
Conky: desktop window (e00035) is subwindow of root window (45)
Conky: window type - override
Conky: drawing to created window (2a00002)
Conky: drawing to double buffer
grep: Temp: No such file or directory
grep: Temp: No such file or directory
Is this a temperature for my Motherboard?
M/B Temp: +39.0°C (low = +0°C, high = +127°C)
Bruce
Lmsensors should allow you to see your temps using conky, and though the terminal.
Step one open a terminal, and type.
If the machine is running dual core you will want to grep for both cores. the above was tested on a Intel set up.Code:sensors | grep -A 1 'Core 0' sensors | grep -A 1 'Core 1'
Amd you can try the below grep
Step two will entail you counting the number of characters shown youCode:sensors | grep -A 1 'cpu0' sensors | grep -A 1 'cpu1'
Example:
The above line is passing the cut command with the -c option. Which specifies character positions, and in this case it would pass characters 13-16.Code:Core0..:: ${freq_dyn_g cpu0}Ghz ::: Usage: ${cpu cpu0}% ${cpubar cpu0 8,50} ${execi 8 sensors | grep -A 1 'Core0' | cut -c13-16 | sed '/^$/d'}C
On the system you are running the characters might be longer or shorter. You would simply count the characters including any spaces/gaps up to the point you want.
Yes that looks to be your main board temp. you can try the below grep.
Hope this helps.Code:sensors | grep -A 1 'M/B Temp'
Advantages and Disadvantages of 64bit.(Plus install Guides)
‘In search of some small measure of peace, that we all seek, and few of us ever find.’
@JMK
bruloo@The-Team:~$ sensors | grep -A 1 'Core 0'
bruloo@The-Team:~$ sensors | grep -A 1 'Core 1'
bruloo@The-Team:~$ sensors | grep -A 1 'cpu0'
bruloo@The-Team:~$ sensors | grep -A 1 'cpu1'
bruloo@The-Team:~$
No results.
EDIT:
But check this out:
bruloo@The-Team:~$ sensors | grep -A 1 'M/B Temp'
M/B Temp: +41.0°C (low = +0°C, high = +127°C)
vid: +1.650 V (VRM Version 8.2)
bruloo@The-Team:~$ sensors | grep -A 1 'CPU Temp'
CPU Temp: +52.0°C (low = +0°C, high = +127°C)
M/B Temp: +41.0°C (low = +0°C, high = +127°C)
Last edited by Bruce M.; January 16th, 2008 at 02:41 PM. Reason: EDIT
Advantages and Disadvantages of 64bit.(Plus install Guides)
‘In search of some small measure of peace, that we all seek, and few of us ever find.’
Bookmarks