├─ 2605 cmdock -c -j 1 -r target.prm -p /var/lib/boinc/slots/4/data/scripts/dock.prm -f htvs.ptc -i ligands> /projects/├─ 2598 cmdock -c -j 1 -r target.prm -p /var/lib/boinc/slots/5/data/scripts/dock.prm -f htvs.ptc -i ligands> ├─ 2040 /usr/bin/boinc -dir /var/lib/boinc Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)Īctive: **active (running)** since Thu 11:50:59 CDT 4h 25min agoĬGroup: /background.slice/rvice ** rvice - Berkeley Open Infrastructure Network Computing Client.See if this helps: (base) sudo systemctl status boinc-client But the manager is a different app from the client service. But might be worth a try.Īnyone see same thing or have any ideas?Ĭheck the service file listed in the output from systemctl status has the hardening been added? If so, copy to /etc/systemd/system and edit out the relevant hardening options and see if it starts up. I think boinc manager shuts down client but I don’t think boinc-client can stop manager from running so I don’t think boinc-client is the cause. I may try uninstall/reinstall of client if I get no other suggestions. I don’t see any boinc eliments in the update of today. Client appears to be running from a view of system resources app as there is activity on 6 cpus dedicated to it. Yast services manager says boinc client is active (running). I uninstalled and reinstalled boinc-manager stilll does not run. I also tried to start it from a terminal. I tried starting it from a desktop launcher after the reboot. Since update this morning that included the various kernel modules which required a reboot, boinc manager does not run.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |