Package: boinc-client
Version: 7.14.2+dfsg-3
Severity: important
Dear Maintainer,
* What led up to the situation?
As title says. I just apt-get install and run boincmgr as usual at the first
time.
* What exactly did you do (or not do) that was effective (or
ineffective)?
When I run the boincmgr, all items grayed out.
* What was the outcome of this action?
This is my systctl status says:
● boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor
preset: enabled)
Active: active (running) since Thu 2019-05-30 08:59:17 CST; 8min ago
Docs: man:boinc(1)
Main PID: 8352 (boinc)
Tasks: 2 (limit: 4915)
Memory: 6.3M
CGroup: /system.slice/boinc-client.service
└─8352 /usr/bin/boinc
30-May-2019 08:59:20 [---]suspend work if non-BOINC CPU load exceeds 25%
30-May-2019 08:59:20 [---](to change preferences, visit a project web site
or select Preferences in the Manager)
30-May-2019 08:59:20 [---] Setting up project and slot directories
dir_open: Could not open directory 'slots' from '/var/lib/boinc-client'.
30-May-2019 08:59:20 [---] Checking active tasks
30-May-2019 08:59:20 [---] Setting up GUI RPC socket
30-May-2019 08:59:20 [---] gui_rpc_auth.cfg is empty - no GUI RPC password
protection
30-May-2019 08:59:20 [---] Checking presence of 0 project files
30-May-2019 08:59:20 [---] This computer is not attached to any projects
30-May-2019 08:59:20 Initialization completed
After mkdir under /var/lib/boinc, it's all perfect and rainbowed in.
● boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor
preset: enabled)
Active: active (running) since Thu 2019-05-30 09:10:21 CST; 4s ago
Docs: man:boinc(1)
Main PID: 10947 (boinc)
Tasks: 2 (limit: 4915)
Memory: 6.3M
CGroup: /system.slice/boinc-client.service
└─10947 /usr/bin/boinc
30-May-2019 09:10:23 [---]don't use GPU while active
30-May-2019 09:10:23 [---]suspend work if non-BOINC CPU load exceeds 25%
30-May-2019 09:10:23 [---](to change preferences, visit a project web site
or select Preferences in the Manager)
30-May-2019 09:10:23 [---] Setting up project and slot directories
30-May-2019 09:10:23 [---] Checking active tasks
30-May-2019 09:10:23 [---] Setting up GUI RPC socket
30-May-2019 09:10:23 [---] gui_rpc_auth.cfg is empty - no GUI RPC password
protection
30-May-2019 09:10:23 [---] Checking presence of 0 project files
30-May-2019 09:10:23 [---] This computer is not attached to any projects
30-May-2019 09:10:23 Initialization completed
Bondezirojn.
From Zhang Xiaowei
-- 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
