The LODA project is now running on BOINC: https://loda-lang.org. It's a maths / computer science project aiming at finding programs and algorithms for integer sequences.

BOINC ADDRESS for the project:
https://boinc.loda-lang.org/loda/
TAKE NOTE OF ADDITIONAL INFORMATION / INSTALLED PROGRAMS NEEDED TO RUN THE PROJET
Prerequisites: LODA runs on Windows, Linux and macOS. You need to have git installed. On Windows, please install Git for Windows. On Ubuntu/Debian, you can install it using sudo apt install git. On macOS, it is included in homebrew.

Currently in discussion on their boards because everything is failing for me and at least one other user.

confirmed to project Admin that /tmp is writeable. Waiting for next suggestion.

Edit: Getting server error trying to report failed tasks now. Server status page shows all OK. My guess is that things have been turned off while they do some more work on things.

Currently in discussion on their boards because everything is failing for me and at least one other user.

confirmed to project Admin that /tmp is writeable.

systemctl cat boinc-client.service

will probably confirm the opposite.

Currently in discussion on their boards because everything is failing for me and at least one other user.

confirmed to project Admin that /tmp is writeable.

systemctl cat boinc-client.service

will probably confirm the opposite.

~$ systemctl cat boinc-client.service
# /lib/systemd/system/boinc-client.service
[Unit]
Description=Berkeley Open Infrastructure Network Computing Client
Documentation=man:boinc(1)
Wants=vboxdrv.service
After=vboxdrv.service network-online.target

[Service]
Type=simple
ProtectHome=true
ProtectSystem=strict
ProtectControlGroups=true
ReadWritePaths=-/var/lib/boinc -/etc/boinc-client
Nice=10
User=boinc
WorkingDirectory=/var/lib/boinc
ExecStart=/usr/local/bin/boinc
ExecStop=/usr/local/bin/boinccmd --quit
ExecReload=/usr/local/bin/boinccmd --read_cc_config
ExecStopPost=/bin/rm -f lockfile
IOSchedulingClass=idle
# The following options prevent setuid root as they imply NoNewPrivileges=tr>
# Since Atlas requires setuid root, they break Atlas
# In order to improve security, if you're not using Atlas,
# Add these options to the [Service] section of an override file using
# sudo systemctl edit boinc-client.service
#NoNewPrivileges=true
#ProtectKernelModules=true
#ProtectKernelTunables=true
#RestrictRealtime=true
#RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX
#RestrictNamespaces=true
#PrivateUsers=true
#CapabilityBoundingSet=
#MemoryDenyWriteExecute=true
#PrivateTmp=true  #Block X11 idle detection

[Install]
WantedBy=multi-user.target
lines 17-39/39 (END)

Which line in that confirms the opposite? If it does, how do I change it so I can let them know?

ProtectSystem=strict
ReadWritePaths=-/var/lib/boinc -/etc/boinc-client

That configuration makes the system read-only for BOINC, with few implicit or explicit exceptions. /tmp is none of those. You could override the configuration to allow /tmp but that would have to be done for every client. Or you could make the application developers aware that they are effectively restricted to the BOINC data directory.

Thanks.

I used

 sudo systemctl edit boinc-client.service

to add /tmp to the read write paths.

Tasks running for longer 4 seconds instead of 1.something cpu time and around 50 seconds run time but still failing with

 195 (0x000000C3) EXIT_CHILD_FAILED

Have also posted your suggestion on the LODA forums. Next step might be to try it in a vm and change the line

ProtectSystem=strict

Developer has now published a version that uses the BOINC data directory as a fall back if /tmp is not available. Got there before I got a chance to try out everything I thought of in a vm in case I mucked it up. That seems to be running fine.

Where/how can I do this?

My understanding from the BOINC forums is that you need to email the people who run the stats sites with the url of your stats page. There is a thread there about this project, I will ask in that because I don't pay much attention to stats myself other than to check whether something is working or not.

Who does the project admin need to email with the url of their stats page to get the project stats onto the external sites?

First thing to check is whether the project is obeying GDPR rules and needs to have the account holder authorize exporting of stats to third party aggregation sites.

Second, most BOINC projects just accept the default location of the server software which has the stats.gz file in the normal location and where the 3rd party aggregations sites would scrape automatically in their stats pull cron job.

---

Second, most BOINC projects just accept the default location of the server software which has the stats.gz file in the normal location and where the 3rd party aggregations sites would scrape automatically in their stats pull cron job.

Presumably someone needs to let the 3rd party sites know about the existence of the project or does that happen automagically once the project is on the BOINC list?

Well only when the BOINC source code updates the all_projects_list.xml file do new projects get picked up.
You normally can always add any new project in manually in the Join Projects picklist.
From what I have seen is usually a "welcome to the BOINC family" type of message from David Anderson at the BOINC site.
Whether any of the 3rd party aggregation sites read those feeds is unknown to me.

---

Dave wrote:

Presumably someone needs to let the 3rd party sites know about the existence of the project ...

Yes. Most often (as with LODA) a BOINC user will ask to enable stats dump and then ask permission for 3rd party stat sites to publish the data.
Then posts appear in the stat site forums requesting the addition of the new project. The exception is Free-DC that stay in the loop independently.

---