file_deleter daemon.
Typically you don't need to customize this.
The default file deletion policy is:
- A workunit's input files are deleted when
all results are 'over' (reported or timed out)
and the workunit is assimilated.
- A result's output files are deleted
after the workunit is assimilated.
The canonical result is handled differently,
since its output files may be needed to validate
results that are reported after assimilation;
hence its files are deleted only all results are over,
and all successful results have been validated.
In some cases you may not want files to be deleted.
There are two ways to accomplish this:
- Run the file_deleter daemon with
the -preserve_wu_files command-line option
(to preserve all input files)
and/or the -preserve_result_files command-line option
(to preserve all output files).
- Include <no_delete/>
in the <file_info> element for a file in a
workunit or result template.
This lets you suppress deletion on a file-by-file basis.
- Include the string
nodelete in the workunit name.
In either case you may need to implement your
own scheme for deleting files,
to avoid overflowing data server storage.
";
page_tail();
?>