Since openrc migration foldingathome can't start more than one process On a dual-core, run first, and fail. Reproducible: Always Steps to Reproduce: 1. Update to openrc 2. run /etc/init.f/foldingathome start Actual Results: $ /etc/init.d/foldingathome start foldingathome | * Caching service dependencies ... [ ok ] foldingathome | * Starting Folding@Home on CPU 2 ... foldingathome | * start-stop-daemon: ./foldingathome is already running [ !! ] foldingathome | * Starting Folding@Home on CPU 1 ... foldingathome | * start-stop-daemon: ./foldingathome is already running [ !! ] On amd64 with =sci-biology/foldingathome-5.0.2-r5
I was able to hack around to make it start. Quick and dirty but it works. In /etc/init.d/foldingathome, add --pidfile ${PIDFILE} to line 35 before --exec, after start-stop-daemon. Even with this variable undefined, it starts just fine. Complains upon stopping, but stops fine thanks to the extra kills in the init script.
if you want it to start up quicker though, add something like PIDFILE=/var/run/folding to /etc/conf.d/foldingathome. This is just a place holder and no files actually go anywhere.
Nice :) Works fine
I was able to incorporate some fixes in the latest (6.02) but it's still not 100% clean. foldingathome | * Caching service dependencies [ ok ] foldingathome | * Stopping Folding@Home ... foldingathome | * Will stop processes owned by UID 104 foldingathome | * Will stop processes of `/opt/foldingathome/amd64-smp/fah6' foldingathome | * start-stop-daemon: no matching processes found start/stop works fine, but the error msg is annoying. I may have to talk to uberlord to find the correct solution.
Created attachment 172001 [details] init script for 6.02 Use pidfile as key when stopping. Solves problem described in comment #4. Tricks with ps/grep/kill replaced with single killall.
I believe this should be FIXED as init script was updated in the tree.
