[CRIU] Configuration directory /etc/criu.d

[Pavel Emelyanov]

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?

-- Pavel

> With a simple .conf file -- It would be much tender to users, who need to change
> some of CRIU options by any reason.
> And each damn time I need to change them - I forget where those scripts lie
> 
> But maybe I'm too carping.
>