8 | | * The inputs and outputs of computation; |
9 | | * Components of application: executables, libraries, etc. |
10 | | * Data for its own sake, e.g. as part of a distributed storage system. |
| 8 | * The inputs and outputs of computation; |
| 9 | * Components of application: executables, libraries, etc. |
| 10 | * Data for its own sake, e.g. as part of a distributed storage system. |
69 | | * On the client, input files are deleted when no workunit refers to them, and output files are deleted when no result refers to them. Application-version files are deleted when they are referenced only from superseded application versions. |
70 | | * On the client, the 'sticky' flag overrides the above mechanisms and suppresses the deletion of the file. The file may be deleted by an explicit [DeleteFile server request]. The file may also be deleted at any time by the core client in order to honor limits on disk-space usage. |
71 | | * On the server, the [FileDeleter file deleter daemon] deletes input and output files that are no longer needed. This can be suppressed setting the 'no_delete' property on the file, or using command-line options to the file deleter. |
| 69 | * On the client, input files are deleted when no workunit refers to them, |
| 70 | and output files are deleted when no result refers to them. |
| 71 | Application-version files are deleted when they are referenced only from superseded application versions. |
| 72 | * On the client, the 'sticky' flag overrides the above mechanisms and suppresses the deletion of the file. |
| 73 | The file may be deleted by an explicit [DeleteFile server request]. |
| 74 | The file may also be deleted at any time by the core client in order to honor limits on disk-space usage. |
| 75 | * On the server, the [FileDeleter file deleter daemon] deletes input and output files that are no longer needed. |
| 76 | This can be suppressed by setting the 'no_delete' property on the file, |
| 77 | or using command-line options to the file deleter. |