segregate client trace output by project

[mikus]

With ever-more powerful systems running more and more tasks, it is becoming difficult to analyze the existing trace files (they accumulate too much unrelated information).

This is a request to provide an *optional* facility to have the trace output messages for a project be recorded in a file in the project directory (instead of in the "composite" file in the BOINC directory).

By separating out the trace messages only relevant to a specific project, it will be easier to analyze "what happened" when only one project shows odd behavior.

[Nicolas]

$ grep 'ProjectName@Home' stdoutdae.txt

[Nicolas]

Since r15559 (10 months ago), the manager's Messages tab can filter messages per project.

To filter the log files, like I said above, use a general text processing tool.