I can't explain why. I did this with Ubuntu 20.04 on my test bench. I opened the file with the standard text editor (gedit) in the GUI, then added <priority>2</priority> and saved and closed the file. restarting BOINC (launched via boincmgr) results in the file being reverted without my edits.

I tried doing this again invoking root privs by running sudo gedit job.xml*, made my edits, saved, and same behavior.

just now, I ran a chown root job.xml* to change the owner to root (instead of me). and it still deleted and regenerated a new file without my edits when starting BOINC back up.

it seems the only thing that makes it stick is the chattr +i command, but then the project doesnt like it, tries to overwrite it, can't, and all tasks stop running.

---

For comparison: different BOINC environment.

I have service install (from Gianfranco's PPA): I have added myself to the boinc user group created by the PPA: I think my file browser's 'administrative' mode is the equivalent of sudo (the same password works for both).

Hi L,
Is it still stable 1 month later ?

And this is what's causing it. As a long time BOINC user you'll know that 0.986 is interpreted as zero

can you cite a source for this? I'm not sure this is the case. please point me to the BOINC documentation or code segment that defines this behavior. the GPU allocation works as intended (0.5 = 0.5, 1=1, 0.33=0.33 and so on) so I have no reason to believe it doesn't account for CPU in increments less than 1 also.

I know by what my PC is doing. I'm trying to use 6 out of the 12 CPU threads for BOINC. I had to cut my CPU setting from 50% to 42% to keep my thread usage at 6. From the picture you can see that acemd3 is using 100% of a thread.

https://www.dropbox.com/s/meaiqoikn80jiua/boinc_usage_gpugrid.png?dl=0

So, now when my PC switches to an Einstein task (the one marked as 1 CPU), my WCG threads drop to 4 rather than 5.

So, now when my PC switches to an Einstein task (the one marked as 1 CPU), my WCG threads drop to 4 rather than 5.

Einstein gpu tasks will take a cpu out of the 'allocated' cpu limit for their gpu task.
Gpugrid tasks do not take a cpu out of the 'allocated' cpu limit.

Neither project is right or wrong, they just work differently under the boinc framework.