The cgmanager binary, as coded by upstream, doesn't write a pidfile when it starts. The error "cgmanager: Unable to write pid file: No such file or directory" appears when the daemon starts. A patch is attached which adds the --make-pidfile --background options to start-stop-daemon. This fixes the issue for me. The issue is reproducible with cgmanager but not cgproxy. I can't explain this, since they both appear to call nih_main_daemonise() the same way and they both have equivalent start-stop-daemon args. Reproducible: Always Steps to Reproduce: 1. /etc/init.d/cgmanager start Actual Results: cgmanager: Unable to write pid file: No such file or directory No /run/cgmanager.pid created Expected Results: service starts without error, and /run/cgmanager.pid exists
Created attachment 405310 [details, diff] proposed patch
Created attachment 405312 [details] emerge --info output
Would it be terribly wrong to patch the cgproxy file in a similar way?
Never mind, I upgraded 0.37 and the issue is fixed. Feel free to WONTFIX. If there was still a reason to fix 0.36-r1, then here's extra info: (In reply to Markos Chandras from comment #3) > Would it be terribly wrong to patch the cgproxy file in a similar way? Strangely, cgproxy writes its own pidfile correctly for me. We wouldn't want two things trying to manage it. FWIW, I've reproduced the issue on a new VM at Rackspace. emerge --sync emerge -a =app-admin/cgmanager-0.36-r1 dispatch-conf # to accept ~ emerge -a =app-admin/cgmanager-0.36-r1
Alright closing since this appears to be fixed in the latest ~testing version
