On Tuesday 29 January 2002 19:22, you wrote: > On Tue, Jan 29, 2002 at 02:31:16PM -0500, Gianni Johansson wrote: > > Optionally configure this line too: > > > > fproxy.params.tempDir=some_dir_with_lots_of_space > > > > If you don't set fproxy.params.tempDir, fproxy will dump it's temp files > > into the "default place" (C:\Window\Temp ???). The problem is that if > > the user kills the node before it has time to clean up its temp files > > they get left behind forever. > > I think calling System.runFinalizersOnExit(true) may help (at least for > SIGTERM kills).
Any objections if I set this in freenet.node.Main() ? We really need an FCP / Admin Servlet command to do a clean shutdown so that people stop SIGINTing the node as is current practice. > > > In a perfect world we would never leak temp files, but since we sometimes > > do, I figured it is better to keep them in a separate dir where they are > > more easily cleaned up manually. > > Why doesn't fproxy allocate temp files from the node's BucketFactory? > (maybe we should include a "freenet.support.BucketFactory" in the > context-wide attributes for servlets). > > -tc I didn't want to pull that much storage out of the node. The current FEC encoder stuff has a disk space high water mark ~= 64MB + file size for big files. Eventually, once the new DS code settles down, maybe same JVM client code should have it's own encrypted datastore for temp files set as a context attribute as you suggest above. If we don't write the key to disk, even if the store file is left behind it would be unreadable. Having fproxy use unencrypted temp files like it does now is kind of underwhelming. --gj -- Freesites (0.3) freenet:MSK at SSK@enI8YFo3gj8UVh-Au0HpKMftf6QQAgE/homepage// (0.4) freenet:SSK at npfV5XQijFkF6sXZvuO0o~kG4wEPAgM/homepage// _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
