"service boinc-client restart" versus "/etc/init.d/boinc-client restart"

[Christian Beer]

Hi,

I found this little odditiy and want to make sure I didn't understand it
wrong.

>From the man page of "service" I conclude that it is just a wrapper that
executes the init-scripts if no upstart script is present. This is the
case for boinc-client.

Due to some problems with nvidia-kernel-dkms I have to restart
boinc-client after a reboot and call "modprobe --force-modversion
nvidia-uvm" before "xhost local:boinc" in the init-script (line 110) to
get the GPU available for boinc.

The odditiy is that calling "sudo service boinc-client restart" doesn't
seem to have the same effect as "sudo /etc/init.d/boinc-client restart"
as the first will not make the GPU available but the second will. I also
get a different output. See below.

Do you have an explanation for this?

> $ sudo service boinc-client restart
> [sudo] password for christian: 
> [ ok ] Stopping BOINC core client: boinc ... waiting ..
> [ ok ] Starting BOINC core client: boinc.
> [....] Setting up scheduling for BOINC core client and children: idle,chrt: failed to set pid 5147's policy: Kein passender Prozess gefunden
> chrt: failed to set pid 5147's policy: Kein passender Prozess gefunden
> chrt: failed to set pid 5147's policy: Kein passender Prozess gefunden
>  chrt failedCould not write to /proc/5147/oom_adj
> . ok

> $ sudo /etc/init.d/boinc-client restart 
> [ ok ] Stopping BOINC core client: boinc ... waiting .
> [....] Starting BOINC core client: boincNo protocol specified
> xhost:  unable to open display ":0"
> [ ok  error ignored, GPU computing may not be possible.
> [ ok ] Setting up scheduling for BOINC core client and children: idle, idleprio.

Regards
Christian