Hello, I have added this to the project file (actually some time ago.
Kern On Thursday 20 March 2008 18:10:12 Frank Sweetser wrote: > Item: Add a "minimum spool size" setting, defining a minimum level of free > space to spool new jobs > > Date: 20 March 2008 > > Origin: Frank Sweetser <[EMAIL PROTECTED]> > > What: Add a new SD directive, "minimum spool size" (or similar). This > directive would specify a minimum level of free space available for > spooling. If the unused spool space is less than this level, any new > spooling requests would be blocked as if the "maximum spool size" threshold > had bee reached. Already spooling jobs would be unaffected by this > directive. > > Why: I've been bitten by this scenario a couple of times: > > Assume a maximum spool size of 100M. Two concurrent jobs, A and B, are > both running. Due to timing quirks and previously running jobs, job A has > used 99.9M of space in the spool directory. While A is busy despooling to > disk, B is happily using the remaining 0.1M of spool space. This ends up > in a spool/despool sequence every 0.1M of data. In addition to fragmenting > the data on the volume far more than was necessary, in larger data sets > (ie, tens or hundreds of gigabytes) it can easily produce multi-megabyte > report emails! ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
