thetower schrieb: > > Here's a log of some very bad things which happen whenever I change the > clock on my Windows XP machine.
You should check your system log regurlarly when you do such things very often. every time change is logged there and this may make your log grow a lot. > This is the entire log file since I > fresh installed to test this. It seems there's no recovering from this > and I have to install from fresh every time afterwards. that's the reason why your spider should use the FCP interface and not ask fproxy for the data. In that case you can interpret DBRs as you like. (and you can check if you even *have* to fetch the new version...). And, last but not least, the problem with frameset sites is away as well - if the manifest file (or alternatively, any metadata on the way to the default document) has changed, the site has changed. if that's no option for you (and appending ?date= to all links is too annoying as well), why don't you set up a second transient node with minimal store and use that one when you change the time? mihi _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
