It's the same as last year, £200 normal winter fuel, plus £300 COL.

sudo usermod -a -G groupName userName

sudo systemctl start boinc-client

Would you ever like to take another look at published contributions?

It is just challenging to integrate further development ideas so that more users can benefit also from corresponding software evolution.

But we do need to add that to the User Manual - thanks for reminding me.

boinccmd  --get_task_summary c
% Done
---
59.74%
28.47%
28.13%
59.65%
---
47.51%

As @CharlieFenton said, error -102 is a file read error.

That points to a problem with the file location, ownership, or permissions. Failure to comply with BOINC's security model is a user or distribution problem, not a coding issue.

• There has to be a password
  
• The client must be listening for that password
  
• The password is only read at startup - you can't add or change it after the client has already started running
  
• The calling program, whether BOINC Manager or boinccmd, has to supply a matching password
  
• If the password is to be read from that file for automatic use, then the system has to be accessing the right location, and have the right permissions set.
  

If Marcus can explain how he's enabled each of those conditions, we can explore further.
-------------
Since the conversation on GitHub fizzled out, I've my own battle with a Linux installation which was returning 'Authorization failure -155'.

I'd used a script in Terminal to invoke boinccmd. It worked under Linux Mint 20, but failed after an upgrade to Linux Mint 21. It turned out after experimentation that the script worked if I started my script in /hdd/boinc-client (my choice of BOINC data directory), but not in the location I'd used previously. I hope that shows how BOINC problem-solving can sometimes take unexpected twists, and can require full clarity of the whole system environment.

Suspending any task for a project disables the work requests for that project. You don't need to set NNT for that project.

<exclude_gpu>
Don't use the given GPU for the given project. <device_num> specifies the number of the GPU to exclude (0..63). If not given, exclude all GPUs of the given type. <type> is required if your computer has more than one type of GPU; otherwise it can be omitted. <app> specifies the short name of an application (i.e. the <name> element within the <app> element in client_state.xml). If specified, only tasks for that app are excluded. You may include multiple <exclude_gpu> elements. If you change GPU exclusions, you must restart the BOINC client for these changes to take effect. If you want to exclude the GPU use for all projects, look at the <ignore_ati_dev>, <ignore_nvidia_dev> and <ignore_intel_dev> options further down. Requires a client restart.

<exclude_gpu>
   <url>project_URL</url>
   [<device_num>N</device_num>]
   [<type>NVIDIA|ATI|intel_gpu</type>]
   [<app>appname</app>]
</exclude_gpu>