conky does not return the wireless values

[emninger]

Conky does not return certain wireless values (like wireless_link_qual or wireless_bitrate). These values are those which are only returned by doing

Code: [Select]

sudo iwconfig.

I tested (also to see if the conky extension is compiled with wlan enabled, and indeed, starting conky as root returns the values correctly. Now, what would be a way to play around this problem?

Is it possible to create a user conky with sudo rights (not really a good idea i think)? Or to make accessible "sudo iwconfig" to conky?

Thanks a lot in advance.

[Rich]

Hi emninger
Have you seen this:
http://askubuntu.com/questions/350409/conky-does-not-display-wireless-info

[emninger]

Hi emninger
Have you seen this:
http://askubuntu.com/questions/350409/conky-does-not-display-wireless-info

No. I only saw the related discussion (without the solution) in the ubuntuforums. Thanks a lot!

Just a practical question: Since the solution consists in changing, partially, the rights of conky, how would they been made persistent since conky (binary) sits - as a symbolic link to /tmp/conky/usr/local/bin/conky - in /usr/local/?

[gerald_clark]

Unlink and copy in bootlocal.sh.
Another option is to copy the conky binary to your ~/bin and run it from there.

[emninger]

Unlink and copy in bootlocal.sh.

But wouldn't any boot recreat that link? And what do you mean by: "copy in bootlocal.sh". I thought of bootlocal.sh as the script starting (my) processes and/or daemons before X comes up?

Another option is to copy the conky binary to your ~/bin and run it from there.

This option i understand better I'd have to create ~/bin, i presume. And to change my path variables (where, which file, btw?)?

[gerald_clark]

bootlocal.sh can do lots of different things at boot, but my second suggestion is easier.


You don't need to change your PATH.
just start it with

~/bin/conky &

in your script in .X.d

[emninger]

Ok. Thanks a lot. Later on i'll try and turn back with the results.

[emninger]

Hi emninger
Have you seen this:
http://askubuntu.com/questions/350409/conky-does-not-display-wireless-info

I tried that solution. Problem starts with the first command (those to give - limited - admin rights to conky):

command:

Code: [Select]

sudo setcap cap_net_raw,cap_net_admin=eip /usr/bin/conky
gives the result:

Code: [Select]

sudo setcap cap_net_raw,cap_net_admin=eip /usr/bin/conky
Which would be the corrispondent command in tcl, if at all?