"Anthony L.Gelsomini" <[EMAIL PROTECTED]> wrote: > > On Friday, April 5, 2002, at 08:37 AM, Lex Spoon wrote: > > > > > > A problem is that if the disk really fills up, LOTS of things will start > > having problems. A better approach would probably be to set a limit in > > some configuration file, and have the server stop accepting uploads if > > that limit is reached. That way, the error can be handled sanely and > > the server will keep running, just without uploads. > > > > > > One simple solution that doesn't require a change in the swiki would be > to implement quotas on the server coweb.cc. is running on. You could > set to like 80% of the disk space so at least the system should continue > to serve requests in theory.
This doesn't seem to work out as well as it first sounds. The swiki itself will still crash when quota runs out. If Apache is running on the system, then whatever Apache is serving would stay available. This subset would not include the swiki pages themselves. We could think about having Swiki export all the HTML to Apache to serve, but this seems like a lot of trouble. Dynamically generating the pages in Squeak is convenient, and in our circumstances the ability to play with new features seems more important than the slightly increased stability. But it doesn't even have to get down to that -- the Swiki code is available, and tweaking it to have a built-in quota should be easier than trying to export all the content to static files. -Lex
