On Fri, Sep 23, 2011 at 03:54:01PM +0200, Jan Safranek wrote:
[..]
> +If one or more config files are specified, only groups defined in the config
> +files are removed. The files are processed in reverse order, i.e. the last
> +file on command line is processed first, so \fBcgclear\fR can have the same
> +command line arguments as appropriate \fBcgconfigparser\fR.
> +
> +.TP
> +.B -l, --load=<filename>
> +specifies the config file to read. This option can be used multiple times and
> +can be mixed with \fB-L\fR option.
Would -f be a better option here?
[..]
> +.TP
> +.B -e
> +specifies that only empty groups should be removed. If a group defined in a
> +config file has tasks inside or has a subgroup, it won't be removed. This
> +option works only with \fB-l\fR or \fB-L\fR options.
> +
So if I have a cgroup hierarchy.
parent
|
child
And there are no tasks in child group. Will both child and parent be
deleted? Or it will depend on the order whether parent's status was
examined beofre child or not.
Thanks
Vivek
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Libcg-devel mailing list
Libcg-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libcg-devel
