refine "don't work while computer in use"

[davea]

Work harder to be invisible to user while computer is in use:

1) don't use CPU if non-BOINC CPU usage has exceeded N% in the last M seconds (e.g. don't compute while user is watching movie on DVD)

2) don't use network while computer is in use

[mikus]

If you make changes, please make sure this new "don't" behavior is optional.

To me as a user, a beneficial characteristic of BOINC's use of the CPU is that BOINC runs in the background. When BOINC interferes with my DVD watching, I am perfectly capable of manually suspending BOINC -- I do not want BOINC to "automatically" assume what my personal priorities are. And I do not care if on Linux my foreground's response time gets worsened by BOINC.

Likewise, let me manage how my network is used - I do not want BOINC to "automatically" assume what my personal priorities are. [Since the client often has to wait for a server response, I sometimes start up non-BOINC processes which also use the network -- this way I can accomplish both activities in parallel, and can take down my network connection that much sooner.]

[Metamorf]

I wish to add my $0.02 to this ticket...

As far as the Linux v6.4.7 is concerned, I would also like to add that 'in use' seems to be defined as keyboard activity only, not mouse. Now, I understand this is a moot point where boinc-client is running on a server box, but is bloody annoying when both the BOINC Manager and Client are running on the same desktop box (since one can name many applications/games that have little or no use of the keyboard).

So, for the benefit of BOINC-ophiles with boincmgr and boinc-client running on the same desktop PC, 'in use' should mean keyboard or mouse activity.