On Tue, Mar 11, 2014 at 2:29 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Tue, 11.03.14 08:05, Thomas H.P. Andersen (pho...@gmail.com) wrote: > >> >> On Tue, Mar 11, 2014 at 4:52 AM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> > On Wed, 05.03.14 23:48, Thomas H.P. Andersen (pho...@gmail.com) wrote: >> > >> >> From: Thomas Hindoe Paaboel Andersen <pho...@gmail.com> >> >> >> >> --system >> >> -H --host >> >> -M --machine >> >> --service-type (options: simple forking oneshot dbus notify idle) >> >> --uid >> >> --gid >> >> --nice >> >> --setenv >> >> -p --property (options read from bus_append_unit_property_assignment) >> > >> > Looks good as far as I grok the completion things. Zbigniew, you know >> > this better than I do, can you OK this? >> >> I was mostly looking for a verification that the list of options make >> are correct: >> >> --service-type: >> simple forking oneshot dbus notify idle > > Corrct. >> >> --property: >> CPUAccounting MemoryAccounting BlockIOAccounting SendSIGHUP >> SendSIGKILL MemoryLimit CPUShares BlockIOWeight User Group >> DevicePolicy KillMode DeviceAllow BlockIOReadBandwidth >> BlockIOWriteBandwidth BlockIODeviceWeight Nice Environment KillSignal >> >> Some of the properties take e.g. a boolean value and we could go on to >> suggest an on/off value but I did not go that far. > > Given that there is --user= and --group= it's a bit pointless to ever > specify User= and Group= with --property, but then again, it will work. > > There are also the LimitCORE=, LimitCPU=, ... props settable now.
Pushed with the extra LimitXYZ's _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
