···
cfg = config.services.boinc;
allowRemoteGuiRpcFlag = optionalString cfg.allowRemoteGuiRpc "--allow_remote_gui_rpc";
9
+
fhsEnv = pkgs.buildFHSUserEnv {
10
+
name = "boinc-fhs-env";
11
+
targetPkgs = pkgs': [ cfg.package ] ++ cfg.extraEnvPackages;
12
+
runScript = "/bin/boinc_client";
14
+
fhsEnvExecutable = "${fhsEnv}/bin/${fhsEnv.name}";
options.services.boinc = {
···
See also: <link xlink:href="http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely#Remote_access"/>
60
+
extraEnvPackages = mkOption {
61
+
type = types.listOf types.package;
63
+
example = "[ pkgs.virtualbox ]";
65
+
Additional packages to make available in the environment in which
66
+
BOINC will run. Common choices are:
69
+
<term><varname>pkgs.virtualbox</varname></term>
71
+
The VirtualBox virtual machine framework. Required by some BOINC
72
+
projects, such as ATLAS@home.
76
+
<term><varname>pkgs.ocl-icd</varname></term>
78
+
OpenCL infrastructure library. Required by BOINC projects that
79
+
use OpenCL, in addition to a device-specific OpenCL driver.
83
+
<term><varname>pkgs.linuxPackages.nvidia_x11</varname></term>
85
+
Provides CUDA libraries. Required by BOINC projects that use
86
+
CUDA. Note that this requires an NVIDIA graphics device to be
87
+
present on the system.
89
+
Also provides OpenCL drivers for NVIDIA GPUs;
90
+
<varname>pkgs.ocl-icd</varname> is also needed in this case.
config = mkIf cfg.enable {
···
chown boinc ${cfg.dataDir}
73
-
${cfg.package}/bin/boinc_client --dir ${cfg.dataDir} --redirectio ${allowRemoteGuiRpcFlag}
117
+
${fhsEnvExecutable} --dir ${cfg.dataDir} --redirectio ${allowRemoteGuiRpcFlag}
PermissionsStartOnly = true; # preStart must be run as root