On Sunday 16 August 2009 08:13:09 Toni Bergman wrote: > I don't know if this has been reported. Finding info on freenet is hard. > > I'm now using 1230 with winxp pro. my computer is gaming spec device. > Problem: The defragmenting of node.db4o is a cool idea. Doing it half assed > and including it without testing is a bad idea. Not saying that has been > done of course, just that if that was the case. > Anyway. > > 1) There's no point defragging a small sized node.db4o > 2) When it's large, say 800 KB (which happens within 2 days of use).. The > defragmenting that happens at boot OR by restarting freenet while defragment > is selected, takes so long that the starting service decides it's a great > idea to tell me it's having trouble starting service since it's taking too > long. In it's infinite wisdom, it leaves node.db4o fucked up with temp files > on the side. > > Considering points 1 & 2. What's the point of having the defragging there at > all? > I set it to defrag everyone's node.db4o once because it shrunk mine by a factor of 10. I did tell it to allow some time, 1 second per KB with a maximum of 24 hours (because very high numbers cause the wrapper to die immediately). 800MB should therefore have been allowed 1 day. It took longer than that or it failed instantly? I don't suppose you still have the wrapper.log? Also you *can* recover in such a case, we do move the old node.db4o, and you can tell it not to defrag in freenet.ini (node.defragDatabaseOnStartup=false). Sorry it took so long to get to you.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[email protected]?subject=unsubscribe
