client: clean up files

[davidpanderson]

A user points out that the client disk usage increases without bound (see below). We need to:

• prune job_log
• delete old app_version files. The simplest way to do this might be to delete files that haven't been used in a month or two.

---

"Does the project job_log have a maximum size or does it get pruned automatically by the client? I have a client that pretty much runs continuously for years. There is a job_log that has grown to almost 50MB in size. This is a 32 thread machine that runs a lot of jobs per day. I suspect it will continue to grow unless there is a specific action taken to delete it. Additionally, there are executable files for applications that have accumulated in the ../project/ directory that are years old and the application no longer runs. Shouldn't the project clean those up from the server side when the application ends? I know I can clean the "mess" up by doing a periodic project reset but that seems like overkill when the BOINC eco-system should clean up after itself. For clients that are not "actively" monitored (I thought the nature of BOINC was to install, start, run in background, forget), this amounts to a disk storage leak. Over time this one client has amassed almost 500MB of unused files with the majority being orphaned executables from long extinct apps. These also include executables from beta tests that don't get cleaned up. This also causes the client_state.xml and client_state_prev.xml to grow. Current sizes for these files are almost 3MB."

[Uplinger]

This is related to #1386 and #2212 I would suggest we close. I suggest we close #1386 and this Issue since there appears to be an active conversation on Issue #2212

Thanks, -Keith

[davidpanderson]

Those don't mention job logs