Boinc port windows 10#

# Override ProtectSystem to allow VBox to run, othewise it can't access /tmp (see ) ReadWritePaths=-/work/boinc-client -/etc/boinc-clientĮxecStart=/usr/bin/boinc -allow_multiple_clients -allow_remote_gui_rpc -dir /work/boinc-client # Note multiple ExecStart lines are allowed, so default in /lib/systemd/system/rvice Then I have my customizations in /etc/systemd/system/: Where both these files are identical and as they were installed. rw-r-r- 1 root root 1111 /lib/systemd/system/rvice rw-r-r- 1 root root 1111 Oct 23 17:54 /lib/systemd/system/rvice So for example, on one of my machines I split boinc into two services, one for CPDN and one for everything else. You can find the systemd 'service' default files in /lib/systemd/system/rvice and also in /etc/systemd/system/ for user 'override' files for settings that you alter.įor the override file either use the systemctl edit command or just create the file yourself and then restart the service. I did some learning about systemd and have a bit better understanding of things now but would like an answer to my question to make sure my suspicion is right.The file in /etc/default/boinc-client is part of init.d and completely separate from the files used by systemd which uses config files not a shell script like init.d. The config file /etc/default/boinc-client didn't seem to have been read. I updated and tried turning on systemd but BOINC didn't behave as expected.

Boinc port windows 10#

Recently, on the latest Windows 10 and 11 updates, WSL2 became Generally Available and systemd became an option one can turn on. I use WSL2 Ubuntu to run Linux BOINC projects and up to recently WSL2 was init.d. I was hoping to get some confirmation or explanation on this. It seems also that to modify start up configuration in systemd, another method is used and the config file mentioned is not read. It appears that the init.d script is used to start BOINC in non systemd installation and the rvice unit file is used to start BOINC in systemd installations. Both the init.d script and systemd unit file point to /usr/bin/boinc, which I assume is the executable. With systemd enabled, trying to start BOINC as above, a message appears that BOINC was started with the unit file rvice that I mentioned. It reads the config file mentioned for any adjustments the user wants to make. systemd not enabled), that's the start up script that one would run directly or with service boinc-client start command. When starting BOINC in standard WSL2 (i.e. That's the script that I was asking about. It's a configuration file for the /etc/init.d/boinc-client init script. it's called boinc-client and it's located in /etc/default/.