Re: [freenet-support] Datastore feature idea
On Fri, 2002-11-15 at 23:27, James Bason wrote: [snip] While I can't answer the question of how Freenet decides to delete and how to prevent this information loss, for the idea of having a "Grow until it breaks" option for nodes, consider that there's going to be two possibilities for those running permanent nodes. You'll have those who want to set it up, run and forget about it unless something breaks. They don't want to have the node automatically grow on them, nor should it. Then you'll have those who will monitor, measure and mess with their running nodes. If they're serious about keeping all data, they'll watch the data store size and up the allowed amount when it's close to full. Why would they need an autogrow option that would apparently be time consuming to implement? Having just upped my node, I understand where you're coming from, but changing the datasize has been made so much easier through the nG convention[1]. Is losing your node uptime really that painful, heh? [1] One of the better user concessions I've seen recently. I really don't want to fiddle with bits and bytes just to set a node size. I wish the bandwith constraints were as easy to set. Or worked properly, but that's just my lazy refusal to do it Properly in the OS that's speaking. -- Aaron Kurtz - GnuPG Key ID ED588CF2 Ignore false slogans. signature.asc Description: This is a digitally signed message part
Re: [freenet-support] Datastore feature idea
James Bason ([EMAIL PROTECTED]) wrote: > I have a question about the Datastore, and an idea for a feature that I don't > see, but would like to have if possible. First, my question: is there any way > to prevent loss of information from my datastore? I'm using build 535, and > I've got plenty of space for whatever Freenet wants to hand me, but I'd > prefer to not lose anything so as to not contribute to DNF's. Set the size of your data store to the size of the file system. > Secondly, along the same lines, an idea for the datastore. For those of us > with more disk space than God, how about a feature where the datastore simply > grows as needed, and a second option (assuming my first question's answer is > a "no") to retain all data. All disks are finite. Set your data store size. > In other words, the datastore simply resizes > itself whenever necessary until it runs out or gets close to running out of > disk space? You're assuming that Java can *determine* when disk space is running low. I'd be willing to bet money that it can't do that. Remember, everything Java does has to be platform-independent. You can't run system("df ."); and then parse the output -- because that wouldn't work on Windows, for instance. You need to tell it how much disk space is available, up front, in the config file. -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg02158/pgp0.pgp Description: PGP signature
Re: [freenet-support] Datastore feature idea
Hi, On Saturday 16 Nov 2002 07:27, James Bason wrote: > how about a feature where the datastore > simply grows as needed ... until it runs out or gets close to > running out of disk space? Are these things possible? Why not just set the datastore size to the same size as the available disk space? (Assuming you're using the native datastore rather than the old monolithic one.) I don't know how fred behaves if the disk fills up before the store reaches its maximum specified size but it might work. Stephen ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
[freenet-support] Datastore feature idea
I have a question about the Datastore, and an idea for a feature that I don't see, but would like to have if possible. First, my question: is there any way to prevent loss of information from my datastore? I'm using build 535, and I've got plenty of space for whatever Freenet wants to hand me, but I'd prefer to not lose anything so as to not contribute to DNF's. Secondly, along the same lines, an idea for the datastore. For those of us with more disk space than God, how about a feature where the datastore simply grows as needed, and a second option (assuming my first question's answer is a "no") to retain all data. In other words, the datastore simply resizes itself whenever necessary until it runs out or gets close to running out of disk space? Are these things possible? And if so, how soon might we seen them imp'd? Thanks in advance :)