Package: boinc-client Version: 7.10.1+dfsg-1 Severity: important Dear Maintainer,
WorkingDirectory option in boinc-client.service was changed from WorkingDirectory=~ to WorkingDirectory=/var/lib/boinc in upstream PR 2419 and this prevents starting boinc-client on Debian based distros. The change was because enterprisey distros have older systemd's that don't support ~ in paths. You'll have to patch boinc-client.service for Debians. Cheers, Juha -- Package-specific info: -- Contents of /etc/default/boinc-client: # This file is /etc/default/boinc-client, it is a configuration file for the # /etc/init.d/boinc-client init script. # Set this to 1 to enable and to 0 to disable the init script. ENABLED="1" # Set this to 1 to enable advanced scheduling of the BOINC core client and # all its sub-processes (reduces the impact of BOINC on the system's # performance). SCHEDULE="1" # The BOINC core client will be started with the permissions of this user. BOINC_USER="boinc" # This is the data directory of the BOINC core client. BOINC_DIR="/var/lib/boinc-client" # This is the location of the BOINC core client, that the init script uses. # If you do not want to use the client program provided by the boinc-client # package, you can specify here an alternative client program. #BOINC_CLIENT="/usr/local/bin/boinc" BOINC_CLIENT="/usr/bin/boinc" # Here you can specify additional options to pass to the BOINC core client. # Type 'boinc --help' or 'man boinc' for a full summary of allowed options. #BOINC_OPTS="--allow_remote_gui_rpc" BOINC_OPTS="" # Scheduling options # Set SCHEDULE="0" if prefering to run with upstream default priority # settings. # Nice levels. When systems are truly busy, e.g. because of too many active # scientific applications started by the boinc client, there is a chance for # the boinc client not to be granted sufficient opportunity to check for # scientific applications to be alive and make the (wrong) decision to # terminate the scientific app. This is particularly an issue with many # apps started in parallel on modern multi-core systems and extra overheads # for the download and uploads of files with the project servers. Another # concern is the latency for scientific applications to communicate with the # graphics card, which should be low. All such values should be set and # controled from within the BOINC client. The Debian init script also sets # extra constrains via chrt on real time performance and via ionice on # I/O performance, which is beyond the regular BOINC client. It then was # too easy to use that code to also constrain minimal nice levels. We still # think about how to best distinguish GPU applications from regular apps. BOINC_NICE_CLIENT=10 BOINC_NICE_APP_DEFAULT=19 #BOINC_NICE_APP_GPU=5 # not yet used # ionice classes. See manpage of ionice (1) in the util-linux package. BOINC_IONICE_CLIENT=3 # idle #BOINC_IONICE_APP_DEFAULT=3 # idle, not yet used #BOINC_IONICE_APP_GPU=2 # best effort, not yet used -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
