my boinc log are to big which makes the manager take a while connecting to the client. any settings i can make which will make boinc behave BETTER?

there are a bunch that are ~18MB, to big...

---

The cc_config.xml has two options to specify the log file sizes.
<max_stderr_file_size>N</max_stderr_file_size>
<max_stdout_file_size>N</max_stdout_file_size>

The default for each is 2MB or 2097152 bytes.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The cc_config.xml has two options to specify the log file sizes.
<max_stderr_file_size>N</max_stderr_file_size>
<max_stdout_file_size>N</max_stdout_file_size>

The default for each is 2MB or 2097152 bytes.

There are persistent reports that the log size limits are only enforced (at least with recent versions of the client) when BOINC starts up. If you are in the habit of leaving BOINC running for extended periods, it is possible for the log to grow beyond the specified size between restarts: my last log rotation happened at 78 MB (but then, I have set the limit at 50 MB...)

Not having a machine full of GPU's I had forgotten that BOINC only checked the logs on starting. Also I use a "del std*.*" in my .bat for most of my machines & generally give them a reboot once every 2-3 weeks.

Perhaps a scheduled reboot at regular intervals would be appropriate for a high end cruncher in order to keep the log file size down.

While BOINC not constantly keeping track of the log file size is probably a good thing we might be nearing a time when some machines would benefit from checking the size at regular a interval. Perhaps a user option to configure "check/truncate BOINC logs every xx days".

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[