[CRIU] [PATCH 1/4] cg: Add ability to dump custom cgroup properties

[Pavel Emelyanov]

On 05/06/2016 04:47 PM, Cyrill Gorcunov wrote:
> On Fri, May 06, 2016 at 04:41:11PM +0300, Pavel Emelyanov wrote:
>>
>> Where do I get criu itself from then? ;)
> 
>>From preboot execution envinronment of course ;-)
> 
> Seriously, it doesn't matter where or how you get it:
> some service may ship it as executable memory slab to
> you, and that's all. Filesystem structure may change
> quickly and at moment (except autofs script) all our
> criu features can be configureed from the command line
> options as far as I remember, and that's good choise.
> 
>>> We might endup is some network backend which would save
>>> images directly on server side/cloud, moreover there might be
>>> no /etc and such on the machine at all. Yes, I know about LFS
>>> and other standarts, but still.
>>>
>>> For vz7 we will need command line options (ie cgroup-props
>>> and cgroup-props-file) because it's convenient to test such
>>> things via cli patching libvzctl scripts.
>>>
>>> Btw, what is the better place for this "cgroup.yaml" file
>>> we gonna use as default one?
>>
>> I don't know. Maybe Tycho can suggest something? Does LX[CD] have
>> some list of default parameters for cgroups and, if it does, where
>> does it keep it?
> 
> We alrady setting up /usr/libexec/criu/scripts/ so maybe keep
> it in /usr/libexec/criu?

I'm not an expert in placing files over linux fs tree :) But the substring
"exec" in the path makes me think that this is a place for executables or
scripts.

> 
> ---
> 
> [root at nun ~]# repoquery -l criu
> /usr/lib64/libcriu.so.1
> /usr/lib64/libcriu.so.1.0
> /usr/libexec/criu
> /usr/libexec/criu/scripts
> /usr/libexec/criu/scripts/systemd-autofs-restart.sh
> /usr/sbin/criu
> /usr/sbin/crtools
> /usr/share/doc/criu-2.1.0.18
> /usr/share/doc/criu-2.1.0.18/COPYING
> /usr/share/doc/criu-2.1.0.18/README.md
> /usr/share/man/man8/criu.8.gz
> .
>