[Bug 1188850] Re: cgrulesengd cannot process symlinked executables

[Serge Hallyn]

Thanks, ojab - tried out your testcase, worked like a charm.  (For
manual reproduction, I'd recommend sleeping 20 rather than 2)

** Description changed:

  Oh hai!
  
  I've found that 0.37.1-1ubuntu10 in precise/LTS cannot process symlinked executables correctly, the testcase is
  >$ python -c "import time; time.sleep(2)" &  cgclassify $!
  >Error in determining process name of pid 9738
  
  The issue was fixed upstream in v0.38, see
  https://sourceforge.net/p/libcg/libcg/ci/acbed86127d5d81d082fa5b90cac13a4f84f877e
  
  It will be awesome if the patch will be applied to v0.37 in precise/LTS,
  because right now cgrulesengd/cgclassify are basically unusable.
+ 
+ ==============================
+ SRU Justification:
+ 1. Impact: symlinked executables cannot be classified
+ 2. Development fix: in the case of a symlink, read the real
+    file path from /proc/self/exe
+ 3. Stable fix: cherrypick small patch from development fix.
+ 4. Test case: see comment #5.
+ 5. Regression potential: there should be none, as this fix is
+    taken straight from upstream and only affects the path when
+    a symbolic link is being run (which is already broken).
+ ==============================

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/1188850

Title:
  cgrulesengd cannot process symlinked executables

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1188850/+subscriptions