On 11/17/2011 04:31 PM, Marco Marongiu wrote:
> Il 17/11/2011 16:22, no-re...@cfengine.com ha scritto:
>> Run your promise in verbose mode and see what Cf is telling apt or
>> aptitude to do. Package promises are very tricky and Cfengine is not
>> really to blame. Many package managers do not behave as expected.
> I'm already doing that. aptitude, but also apt, run dpkg, which in turn
> hangs asking questions about what to do with some configuration files it
> found in the way.
>
> I can, of course, circumvent this specific behaviour, and I know that
> package managers may not be well suited for non interactive actions.
> Still, I find that cf-agent not being able to bail out of such a
> situation is kind of a bug. And a bad one.
There is not much CFEngine can do about kernel bound things like I/O,
except to try to kill the source process.
Unfortunately, Linux does not support sigalarm timeouts in a lot of
calls so it is hard to know when something is hanging. The usual
approach for debian systems is this:
body agent control
{
environment => { "DEBIAN_FRONTEND=noninteractive", "LANG=C" };
}
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
