[CRIU] Configuration directory /etc/criu.d

[Jeremy Cline]

On 08/12/2016 11:00 AM, Pavel Emelyanov wrote:
> On 08/05/2016 09:31 PM, Adrian Reber wrote:
>> On Fri, Aug 05, 2016 at 09:19:13PM +0300, Pavel Emelyanov wrote:
>>> On 08/05/2016 07:50 PM, Dmitry Safonov wrote:
>>>> 2016-08-05 19:02 GMT+03:00 Adrian Reber <areber at redhat.com>:
>>>>>
>>>>> Having added the skip in-flight TCP connections option to TCP I thought
>>>>> something else is needed to influence CRIU's behavior. Every tool using
>>>>> CRIU (docker, lxc, runc, ...) hardcodes the required options into the
>>>>> source code and every change to CRIU requires a change in all tools.
>>>>>
>>>>> Therefore I thought it would be nice to have something like
>>>>>
>>>>> /etc/criu.d/ or ~/.criu.d/
>>>>>
>>>>> where CRIU would look for .conf files which can enable or disable
>>>>> options for all CRIU invocations.
>>>>>
>>>>> Staying at my skip in-flight TCP connections example I could just add a
>>>>> file to /etc/criu.d which always enables --skip-in-flight for CRIU
>>>>> invocations on that system. There should then also be a way to disable
>>>>> options from hardcoded CRIU invocations in higher tools like docker and
>>>>> lxc. I would also expect an option to ignore files in /etc/criu.d.
>>>>>
>>>>> https://github.com/xemul/criu/issues/194 is good example where it could
>>>>> also help.
>>>>>
>>>>> Is this something which would be useful to CRIU? Any other opinions?
>>>>
>>>> In my point of view -- it's a nice idea.
>>>> I'm not a huge fan of scripts like that are being used in Virtuozzo
>>>> distributions
>>>> for suspending/resuming containers.
>>>> If we could like substitute scripts like that:
>>>> https://github.com/OpenVZ/libvzctl/blob/master/scripts/vz-cpt.in
>>>
>>> I doubt we would be able to fix _all_ of this with /etc/criu.conf, but
>>> having a file with criu opts _defaults_ sounds like a good idea indeed :)
>>>
>>> By the way...
>>>
>>> Does anybody have examples of config files in /etc for CLI tools (!), not
>>> daemons/services or system startup configurations?
>>
>> wget, curl, mutt
>>
>> All of them have config files in /etc
> 
> Cool :) Then let's do it also. It looks like the first candidate for this
> config file would be the --ghost-limit one :D

I'm interested in doing this work in order to get familiar with the
CRUI development process and code base. However, it'll be a project I
work on in my personal spare time and I don't expect to have much of
that until September so it'll be a few weeks before I can start working
on it.

-- 
Jeremy Cline