I don't use it for my ISP. I like the details to see.
I don't use it for my ISP. I like the details to see.
Well that's the beauty of Conky I can display information you wouldn't want and you can display vnstat I don't want.
I've changed Conky from the post an hour ago to include Net totals at the bottom and CPU load average near the top. I've taken out the Swap disk lines which were almost always ZERO anyway.
With lots of Chrome tabs open the load average is over 2.00 which is theoretically bad for a dual core CPU yet response time is still snappy. I can do more fine tuning of Google Chrome flags and experimental plugins if I feel sadistic / masochistic.
Does anyone know why ${alignc} (align text to centre) doesn't work?
Does anyone know why {print int(53*100/70)}% shows up as text instead of the calculated result of 76%?
TIA
Last edited by WinEunuchs2Unix; August 17th, 2014 at 08:26 PM.
A new group of conkys - nine in all made for the wallpaper 1920x1080 - grimy_wall_by_alpha_10-d7bvin6.jpg (included in the archive)
Grimy_Wall
File available at Deviant Art Conky Group - 6.6MB Zip
clock by easysid (modified) (See README)
lats and longs and email by Kaivalagi (See README_II)
Last edited by Sector11; August 19th, 2014 at 12:51 AM.
^ Shhhhhhhhhhh still two days to go and thank you.
Can anyone of you "conky pros" tell me if there is now a way to get the CPU model except for cat'ing /proc/cpuinfo?
I always think it's a bit clumsy executing a system command when there is a variable you can use instead.
Of course, 8 years ago (!!) when this thread was created, this did not exist.
But as conky has now advanced by many version numbers...perhaps now...?
Sorry but, not according to: Conky Objects (below TEXT). Another useful page is Config Settings (above TEXT). I use to keep text files of these pages but the links are better as they are always up to date.
Conky still needs something like this - I don't use "cat":
Suggest: pre_exec - after all, not like your CPU is going to change every 10 seconds or soCode:${pre_exec grep 'model name' /proc/cpuinfo|sed -e 's/model name.*: //'|uniq} ${pre_exec grep 'model name' /proc/cpuinfo|sed -e 's/model name.*: //'|cut -c 1-10|uniq}\ ${pre_exec grep 'model name' /proc/cpuinfo|sed -e 's/model name.*: //'|cut -c 15-20|uniq}
pre_exec
shell command
Executes a shell command one time before conky displays anything and puts output as text.
THANKS for pre_exec! Of course I wanted to avoid at all costs that the CPU info would be read multiple times off /proc!
So this would become mine then (a little less typing perhaps; it helps to know that the white space after 'model' and 'model name' consists of tabulators, not spaces, which is why the grep will skip the 'model' line)
Code:${pre_exec grep 'model ' /proc/cpuinfo | cut -f3- '-d '}
Last edited by syntaxerror74; August 23rd, 2014 at 08:38 AM.
Bookmarks