To install libwebkitgtk run, sudo apt-get install libwebkitgtk-1.0-0

Thanks Keith for all that.

Correct me if I'm wrong but isn't it?

sudo apt-get install libwebkitgtk-1.0



Z

---

Yes, you should just drop the trailing zero.

I wont get a chance to try this solution for another 6 hours, but...

If you check host id: 153837 and 423329. (both belong to same user, [not me])

Both running Boinc client 7.8.3 and have been using SPIN since at least 21st October (possibly longer)

Can't tell just from the Host details which and where from the hosts obtained the BOINC 7.8.3. It very well could be the TBar version so explains why it works.

This user participates in lots of projects, Seti being one of them and could very well have installed the TBar BOINC 7.8.3 version.

I've managed the BOINC client (installed from the repo) to notice the SWAN_SYNC=1 parameter (in /etc/environment).
(BTW it has to be spelled with all caps to work.)
By default the BOINC client runs under the account called 'boinc', as a daemon (system service).
When it runs this way, it won't regard the environment settings in /etc/environment.
So I stopped the BOINC daemon by opening a terminal and elevating it with

sudo su

then

/etc/init.d/boinc-client stop

then I changed dir to the BOINC data dir with

cd /var/lib/boinc-client

then I've started BOINC with

/usr/bin/boinc

It will run as 'root' and it will have the proper environmental settings, but it can't be managed through the graphical interface.
The acemd will use a full thread, which is 25% CPU on my Core i3 (I've checked it)
The result is amazing: 6.872 sec for a PABLO_2IDP_P01106 task (110.400 credits). It took 8.800 seconds without the SWAN_SYNC.
My GTX 1080Ti got 28% faster by applying SWAN_SYNC=1.
You can check my hosts:Host 391255, Host 482653

Thanks for the update. I had a hunch the issue with the repository version was because of the account "boinc" permissions preventing the system wide environment variable not being picked up.

The TBar BOINC versions avoid this issue since both the client and Manager are installed and run under the user account.

Thank you and trying now.

Is there a way to manage via another manager, like BAM, while in this state?

You should still be able to control the client with the boinccmd tool.
Controlling_BOINC_remotely

As far as using another manager, you could install Wine and then install BoincTasks to manage the client.

I found BoincTasks indispensable when I was running Windows, so the first thing I did after moving to Linux was to investigate whether BoincTasks would run under Linux. It does, quite well in fact. So I have Wine installed on my daily driver that I sit in front of 8 hours of the day and I control and monitor my 4 other hosts from that chair without having to get out of it and sit in front of the other hosts to interact with them.

BoincTasks, TThrottle

I am running SuSE Leap 15.0 on two Linux hosts. BOINC 7.8.3 is given to me by SuSE. One is running QC only, no graphic board, the other both QC and acemd on its GTX 750 Ti, CUDA 80, BLOCKED parameter.
Tullio

We think it doesn't matter what the BOINC version is . . . if it comes from a repository and is installed as a daemon with the user 'boinc', it is not going to allow the SWAN_SYNC=1 parameter to be enabled on gpu tasks.

Only the Seti user developed BOINC versions which are installed in /home with the user the owner use the parameter correctly.

Retvari Zoltan has figured out a method around the repository versions but without Manager control of the client.

ALAIN's second work unit returned also with BLOCKING still in the stderr. So it is not picking up the SWAN_SYNC=1

Thanks to everyone who is reporting back with their results.

I think it maybe necessary to use the BOINC Manager version compiled by TBar at crunchers anonymous in order to get it to work properly.


http://www.arkayn.us/lunatics/BOINC-7.8.3.7z

The default of the BM is set to connect to Seti@home but you can always add GPUGrid as a project and then delete the Seti@home folder.

SWAN_SYNC variable is setting
but BOINC don't read it

---

My workaround in my previous post is just a temporary solution (it's fine for me for the time being).
To completely solve this issue we should:
1. change the owner of /var/lib/boinc-client to the user (I know how to do that, but it's pointless if I can't do the next steps).
2. change the user account under which the boinc daemon starts. There should be a Linux configuration file containing this setting, which I haven't found yet (it's not enough to change the BOINC_USER in /etc/default/boinc-client and in /etc/init.d/boinc-client)
3. the user should have the right to start a daemon (at least in Windows it works that way).

I have successfully automated the start of boinc client.

It does weaken the security of the installed boinc package so use at your own risk!!

in the service control file /lib/systemd/system/boinc-client.service:
Under [service] heading, make this the first line
Environment="SWAN_SYNC=1"

Under [service] heading, change User=boinc to:
User=root (this is the line that weakens security)
EDIT: as per testing by Retvari Zoltan, this line does not need to be changed. It can stay as User=boinc (and hence not compromise security). Thanks Retvari Zoltan

You do not need to add SWAN_SYNC=1 to the /etc/environment file as a service creates it's own environment(my understanding)

reboot. (easiest way to implement)

run top in a terminal (or your favourite GUI task manager) to check acemd process is using 100% of cpu

Success! I did the steps recommended by Retvari Zoltan and then also installed Wine and BoincTasks (thank you Keith Myers) in order to have a manager (which installed very nicely and automatically 'synced up' with the running Boinc Client).

As implied by Zoltan's follow-up post, I did realize I had to leave the terminal open with the root-level Boinc Client running.

Overnight, my PABLO WUs processed about 8 percent faster.

http://www.gpugrid.net//results.php?hostid=487152

Looks like more ideas flowing here -- I will wait until this evening to set up my second host and see what else is discovered.

in the service control file /lib/systemd/system/boinc-client.service:
Under [service] heading, make this the first line
Environment="SWAN_SYNC=1"

This is the configuration file I was looking for. Thanks!

Under [service] heading, change User=boinc to:
User=root (this is the line that weakens the security)

I've tested it without changing the user, and it's working, so you don't have to compromise the security of the system.

Thanks for the feedback, will reset
User=boinc as you suggested!

Zoltan, now that you've tried all of the potential solutions, what do you think is the easiest, safest, and most fool proof?

Zoltan, now that you've tried all of the potential solutions, what do you think is the easiest, safest, and most fool proof?

Rod4x4's solution is the perfect one.
I've also made a post in the "SWAN_SYNC in Linux client" thread based on his solution.

Thanks for the feedback, will reset
User=boinc as you suggested!

My tasks that are started as 'root' won't continue after I've started the BOINC manager as 'boinc', so don't be surprised if you have to manage this (aborting the task, or deleting the files from the slot as 'root').

I am running both python and acemd as user tullio, so I have almost the whole 1 TB disk available to BOINC 7.8.3.
Tullio

Success! I did the steps recommended by Retvari Zoltan and then also installed Wine and BoincTasks (thank you Keith Myers) in order to have a manager (which installed very nicely and automatically 'synced up' with the running Boinc Client).

As implied by Zoltan's follow-up post, I did realize I had to leave the terminal open with the root-level Boinc Client running.

Overnight, my PABLO WUs processed about 8 percent faster.

http://www.gpugrid.net//results.php?hostid=487152

Looks like more ideas flowing here -- I will wait until this evening to set up my second host and see what else is discovered.

Add --daemon to the boinc client startup command to allow the client to run w/o an active terminal. That's how I start multiple clients on a PC.