[systemd-bugs] [Bug 73685] New: Allow resource controls on systemd-run

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 15 23:07:12 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=73685

          Priority: medium
            Bug ID: 73685
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Allow  resource controls on systemd-run
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: enhancement
    Classification: Unclassified
                OS: All
          Reporter: sss at lambdacurry.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

systemd-run is actually very nifty to run programs in a resource controlled
mode. It is pretty much a better "isolate"
(http://www.ucw.cz/moe/isolate.1.html).

The problem is that systemd-run does not allow programs to be run with resource
controls. I am aware of the --slice parameter, but that is an umbrella resource
control:  If I run 5 different programs simultaneously (with differing resource
requirements), It does not let me allocate resource control on a per run basis.
The other solution suggested to me on IRC was to issue a "systemctl
set-property" after firing the systemd-run, which really does not serve the
purpose.

I tried passing a .service file to systemd-run (which allows specification of
resource controls within it), but it doesnt seem to execute it. In fact, I
would argue that systemd-run should simply read in a .service file (which has
all the --slice and --scope parameters built in), honor the resource controls
and execute it. You can ignore the dependencies, etc. which are not required.
All the commandline arguments would be unnecessary.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140116/b23b7c19/attachment.html>


More information about the systemd-bugs mailing list