On 2013/03/18 22:42, Martijn Rijkeboer wrote:
> > cfengine does not run after installation, either copy some basic
> > policy files or provide real README.
>
> Attached is a new version of the README is this what you meant?
>
>
> > Event it is declared to be built statically it is not, thus it
> > cannot run from /var/cfengine without /usr/local mounted. Which
> > is quite ridiculous... :) I haven't been successful how to built
> > it statically correctly :(
>
> I didn't succeed either and since the official binaries are not statically
> linked I don't think it will work.
>
>
> > 1. patch for configure is useless, drop it
> > 2. add FAKE_FLAGS += examplesdir="${PREFIX}/share/examples/cfengine
> > to meet OpenBSD standards
>
> OK
>
> Kind regards,
>
>
> Martijn Rijkeboer
| Setup policy hub/server
| =======================
|
| To setup a policy hub/server execute the following commands as root:
|
| # mkdir /var/cfengine/masterfiles
| # cp -pR ${LOCALBASE}/share/cfengine/CoreBase/* /var/cfengine/masterfiles
| # cf-agent --bootstrap --policy-server <own IP-address>
Would it be appropriate to @sample these in the PLIST?
| Edit login.conf
| ===============
|
| Consider bumping the openfiles-cur to at least 256 in login.conf(5) for
| the daemon class.
I don't know cfengine at all but if this is for something running
as a daemon, better to provide an rc.d script and tell people to
add a dedicated class (see example in mysql readme). rc.d scripts
ensure that the correct class is used, whereas otherwise somebody
starting from a command line via sudo could easily end up using
another class.
