Jonathan de Boyne Pollard:
To anyone running the service manager and bundles from nosh version
1.28 or later on Linux: You are encouraged to look at your control
group hierarchy, with a tool like "systemd-cgls /", with the "cgroup"
field of the ps command, or by simply listing your
Guillermo:
I suppose the interesting suprise is that as consequence, when a
service definition gets 'imported' to nosh from a unit file (and this
covers pretty much everything in the nosh-bundles* binary
packages),the corresponding service gets placed in a cgroup of its own
when launched by
2016-12-07 6:26 GMT-03:00 Jean Louis:
>
> On Wed, Dec 07, 2016 at 09:14:00AM +, Jonathan de Boyne Pollard wrote:
>> [...]
>> To anyone running the service manager and bundles from nosh version 1.28 or
>> later on Linux: You are encouraged to look at your control group hierarchy,
>> with a
Casper Ti. Vector:
But I do think the capability argument has its validity: chainloading
is, at this time, not well known to normal users, which is why many
systemd supporters compulsorily identify cgroup support with systemd
with few people opposing. Therefore I suggest to add some examples
Many thanks :)
On Tue, Dec 06, 2016 at 12:53:14AM +, Jonathan de Boyne Pollard wrote:
> * http://jdebp.eu./Softwares/nosh/guide.html
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19)
7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
Casper Ti. Vector:
the docs are in tarballs on jdebp.eu
* http://jdebp.eu./Softwares/nosh/guide.html
Sorry, my fault. I read the page in a hurry, and thought the page did
not contain ulimit when the reply said capability control was not
involved in your page. Impatience is really a sin :(
Nevertheless, if you do plan to create a separate page for cgroup
support, I think a brief introduction of
Casper Ti. Vector:
one example for ulimit
An irony here is that the page *already contains* two entire sets of
examples that set memory resource limits, using daemontools,
daemontools-encore, freedt, perp, s6, and nosh tools.