Workunits marked with 49-50 being distributed, so the whole batch will run out on the weekend.
There are 12389 workunits ready to send at the moment, but it will drop very rapidly.
Brace yourselfs for the empty queue.

EDIT:
The nuber of workunits is dropping by 870 per hour, so the queue will run dry on saturday around 15h UTC.

Hello Is anyone getting any work.

Yes, just have to use a update script.

Thankyou My work units have been running fine for the last week,I have altered nothing as of reicving work units.I have used update button and i do not understand update script!!! I have not had any work units for 24 hours?

The tasks are getting fewer and fewer.
I have a backup project that runs when i don't have active GPUGrid tasks.

KeithM is referring to a small program that can be programmed to click update on a regular basis like every minute automatically. Simple mouse programs up to full automation suites will work.

Easier to just use a command line instruction in a terminal and use the provided Boinc boinccmd.

If using Linux, simple as opening a terminal on the host and running:

watch -n 900 ./boinccmd --project https://www.gpugrid.net/ update

Same thing can be done in Windows via command terminal or PowerShell window.

This will ping the scheduler with a update command every 15 minutes.

This way is automatic without having to sit in front of the computer and click a mouse continuously.

Easier to just use a command line instruction in a terminal and use the provided Boinc boinccmd.

If using Linux, simple as opening a terminal on the host and running:

watch -n 900 ./boinccmd --project https://www.gpugrid.net/ update

Thank you so much. I did not know this command. Very helpful and it works.

Toutes les 900,0s: .... pascal-Intel-Z790-Workstation: Tue Feb 4 21:17:16 2025

sh: 1: ./boinccmd: not found

j'ai essayé la commande mais cela ne marche pas pourquoi svp.



I tried the command but it does not work why please

---

You must issue the command from a terminal window after changing to the directory in which the boinccmd executable is located.

merci

thank you

---

for normal boinc installs, boinccmd will usually be available globally.

so you do not need the "./" prefix and you can run it just as

boinccmd --project ... and so on.

---

Thank you.