Menu
▾
▴
#81 Conky hangs for ~5 seconds
Every so often Conky will hang for ~5 seconds without
updating on my screen. If I have something covering it
and move it... conky will not be visible. for a few
more second. I'm not actually sure if this is a bug
with conky. I also am really not sure how to
investigate it farther.
Logged In: YES
user_id=1367985
Originator: NO
Please provide information when posting bugs: conky version, distro, your .conkyrc.
Logged In: YES
user_id=1331921
Originator: NO
This happens for me as well, on Ubuntu Edgy Eft with Conky 1.4.2, if I copy /usr/share/doc/conky/examples/conkyrc.sample.gz to .conkyrc - For me, it's because the configuration uses rhost in a tcp_portmon, and conky is hanging while the lookup is timing out. I don't know what can really be done about this, but at the very least, might it be advisable to cache a table of ip addresses to hostnames to prevent redundant lookups? Even if the delay is unavoidable, that would at least limit the ~5 second delay to once per unknown host. Is this still an issue on 1.4.4?
Logged In: YES
user_id=1367985
Originator: NO
If your computers are on a LAN with private IP addresses,
e.g. 192.168.0.2, 192.168.0.3, etc. you want to make sure
that you have entries for these ip's in your /etc/hosts files.
/etc/hosts
----------
192.168.0.2 yourcomp yourcomp.yourlan.net
etc etc.
Otherwise you are asking your ISP to resolve these private ip's for you,
and that may be causing delays.
Another suggestion I have is to use rip and lip instead of rhost and lhost
with tcp_portmon, i.e. dont bother hitting your (slow) DNS servers. Asking
conky to cache DNS lookups is not the answer.
Logged In: YES
user_id=1331921
Originator: NO
Oh, I understand that - I've already changed to using rip instead, and my major qualm is with the example conkyrc in Ubuntu - But caching the DNS lookup would allow you to only incur the performance hit once, rather than every time conky updates. It may be something of a hack-ish workaround, but rhost seems to be completely unusable on the Internet without it.
Logged In: YES
user_id=1346238
Originator: NO
I believe the original poster's problem was related to Xdamage, but I cannot be sure from the details provided.
As to the problem with slow dns, I'd suggest running your own caching nameserver. There are enough standalone products available, some of which are quite lightweight and quite good, that adding this functionality would be rather redundant.
If you are using a router, most already come with built-in caching nameservers. Otherwise, I'd suggest looking into a project such as djbdns's dnscache (http://cr.yp.to/djbdns.html). Other than dnscache, there's also dnrd (http://dnrd.sourceforge.net/) posadis (http://www.posadis.org/posadis), and many others.
Logged In: YES
user_id=1331921
Originator: NO
Fair enough, that's definitely an option, and it's true that it would be somewhat redundant to put into conky, but at the very least, wouldn't it be best to have the dns queries running on a separate thread, such that it would first display just an IP address and update to the name if it becomes available? Since it's already using IP address as a fallback when the dns request times out, it seems like it would allow a more responsive conky with no features sacrificed.
Logged In: YES
user_id=1367985
Originator: NO
I would go further to say that *all* sampling work should be done in threads.
Future directions will rectify the problem. I am closing this bug. Thanks
for your input.
Logged In: NO
is it possible to prevent conky from doing lookups? and just show the IP address. most of what conky usually showed for me was my IM connections.but I just wanted to know if other connections were being maintained. would it be possible to have conky have an exclude list? exlude these known IP addresses from the connections you display?
Logged In: YES
user_id=1346238
Originator: NO
As mentioned earlier, using the *ip rather than the *host directives will cause conky not to do dns lookups at all.
Logged In: NO
I'd like to just mention that I totally disagree.
I don't think DNS caching in conky would be redundant at all. Why can't conky just identify that the ip address hasn't changed, and thus the dns address hasn't changed? I do run a private dns server, but even with dns caching it can still get bogged down with conky going at 6 dns requests/second plus whatever else is running on that server and on my network. It just seems like a simple feature, not at hack at all, that would save a lot of wasted resources. Simply, I can't see why you'd intentionally want it sending out dns requests at every refresh.
Another happy alternative would be something which I'd really like to see in conky anyway, and that's ability to set individual timers on every element. For example, things like say, the clock, might be nice to have update once a second, whereas things like my ip adress, might need to update a little less often.