Forum: CFEngine Help Subject: Running cf-execd on OSX Author: dpullman Link to topic: https://cfengine.com/forum/read.php?3,26050,26050#msg-26050
We've run cfengine 2 for years on OSX, various versions. To get cfexecd to work with launchctl, we used cfexecd -g to keep it in the foreground. Launchd wants systems processes to not call daemon or fork or otherwise exit as it will think it has died. This has worked well for a long time. We're trying to get converted to cfengine 3, but we've run into an issue with cf-execd. There appears to be no -g option, only a -F (Foreground). However, the behaviour is different. With -F it appears to run once and exit, which causes launchd to respawn in about 30 seconds. Without -F, we get multiple cf-execd processes, which is no good. I posted a bug report in January, but it's still in a new status (ID 0000914). Mikhail, a developer, posted a suggested workaround to use -v as it will cause it to not fork, and that works but it fills up the local system.log. So I thought while we're waiting I'd would ask the community if anyone is running OSX and if you have any suggestions on getting cf-execd to run better than we have so far. Thanks very much. David _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
