Challenging you to venture into the scary cc_config manual yourself and find the answer ;?

(there's 2, yes two options, an old to influence the log file size and a new [I've never tried] to influence how much is shown in the log pane)

edit: Maybe there's Beta fatigue developing... me clients are on a second helping of the 'only 20,000' (which I interpret a 2x20K). None of the first found a wingman yet.

Seke, I accepted the challenge:
<max_stdout_file_size>104857600</max_stdout_file_size>

I'm going to try 100 MB max size

On another topic, some fatigue might have an advantage, more jobs left...

Thanks to Lawrence too

7.28 is looking good: 3 of my Betas have turned Valid, all 3 of mine were suspended/resumed at least once with LAIM off, all 3 wingmen showed only one Initializing line, my Result.out was identical to each wingman's.

[OT]Did write 2 settings... you missed the one that changes the number of lines held visible in the Event window, although, not sure if it's a replacement of <max_stdout_file_size> to just expres the log in lines instead of bytes. Those who test will know... yes it controls the number of lines held in the event view [begins with just start-up log after client boot] ;>)

(warning: Going overboard on log file size and active event window lines may impact BOINC Manager responsiveness... same as buffering too many jobs)[/OT]

On Topic, 3rd helping for 18 of 22 cores [4 of batch 216 are into 7th hour at ~45%], and too having a "LAIM off suspend" treatment (Rickjb, first suspend all 'ready to start' tasks that are not Beta before the LAIM game... had a more complex dance on one machine that had 7.26 prod. running too, so had to alternate LAIM in between to keep those in memory to not risk them going invalid).

BTW, noticed on me 'crunch only' Linux-64 quad & W7-64 octo, that the efficiency is showing as > 99.9% [the CPU : Elapsed ratio]. Did not pay close attention how this is prior and after a restart so screenshotted a before and after and find there's no particular % efficiency shift... no lost time recorded. Greater than 99.9% is incredible... very lean code [but then there's enough RAM to work with... no swapping needed], also a testament to the OS's going largely into snooze mode, purely servicing our crunshing. The W8.1-64 is slightly less efficient, but noticed if you explicitly sign-out not just lock screen, to get 1% better performance i.e the Metro/Modern active tile-interface may keep sucking CPU juice to keep the background fresh, for when screen up again [for those who wish to squeeze the last percent]. Eagerly waiting on 8.2 [seems to be in the works with a quasi-permanent return to the W7 like GUI... eclectic I suppose]