This is a continuation of a discussion on twitter 140 characters just isn't enough for this conversation :)
Quick History, Nick Silkey was trying to setup a new temporal hub against localhost. Guessing he was running cf-agent -B -s 127.0.01 or cf-agent -B -s localhost. Its known behavior. https://cfengine.com/bugtracker/view.php?id=1064 https://github.com/cfengine/core/commit/5ec32e5cdf60f11992e96484b49725872ebea349 The real question seems more to be about how to go about setting up a client to execute policy without a policyhub. CFEngine doesn't need a policyhub. Its the common use case, and the bootstrap flag provides some conveniences for grabbing that first set of policy. Trust keys, some boilerplate policy etc ... That bootstrap or default policy is designed to get you going quick (with a hub, or a client connecting to a hub). It seems logical that your hub could be localhost but that is not allowed. There are some licensing implications for the enterprise version if that were changed. There are some other reasons but they aren't technical. If you aren't going to have a policyhub and are only going to execute local policy then there is limited usefulness to the bootstrap convenience because that default policy is tailored to the common use case. If you want to have some policy to start with just grab everything from /var/cfengine/share/CoreBase and copy it to /var/cfengine/inputs. You probably want to edit promises.cf to disable cf-serverd and failsafe.cf to change the way updates are handled. Once thats done just start the cfengine service or run cf-agent with that policy. It will take care of starting cf-execd and cf-serverd if you choose to keep running it. On the next host just drop your policy into /var/cfengine/inputs and run cfengine. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
