Haxe wrote: > The description of the Checkbox says: > "Whether the clock of this host is kept accurate via NTP. When set, the > computed clock skew is ignored. Normally, gtk-gnutella automatically > determines whether you are running NTP locally, but it won't be able to > determine whether your host is kept synchronized by regular calls to > ntpdate, for instance."
Well, that's the old tooltip text from before ntpd detection was implemented. So this option should either be removed from the GUI or really override the detection result. Switching options behind the users back is simply a violation of POLA. > To me, this sounds exactly like my case, so that I should set this. > And that makes sense to me. I keep my clock accurate, but in a way that > GTKG cannot autodetect, so I inform GTKG about this fact via setting > the option. The old clock skew calculation was much worse than the current one. What clock skew does GTKG report for your system? If it's less than 10 seconds I wouldn't care. Also running ntpdate from cron isn't considered a good practice to keep an accurate clock b/c it will most likely cause a jumping clock everyonce in a while. ntpd is a fat piece of process but if you have 128MB or more, I wouldn't mind and run ntpd (ntpd usually uses 2-3MB). -- Christian
pgpwC8151hUFS.pgp
Description: PGP signature
