Summary: | app-admin/cgmanager-0.36-r1: Unable to write pid file: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Erik Mackdanz <stasibear> |
Component: | Current packages | Assignee: | Markos Chandras (RETIRED) <hwoarang> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
proposed patch
emerge --info output |
Description
Erik Mackdanz
2015-06-18 03:34:19 UTC
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 |