> First of all, I'm not native English speaker :D What about this one?
> Partly based on Debian package.
I'm also not a native English speaker...
> $OpenBSD$
>
> +-----------------------------------------------------------------------
> | Running ${FULLPKGNAME} on OpenBSD
> +-----------------------------------------------------------------------
>
> OpenBSD cfengine port has some tweaks differenting from standard cfengine
> community installation.
>
> As cfengine on OpenBSD is not built statically and depends on libraries
> in ${LOCALBASE}, this questions auto-repairing funcionality of cfengine
> itself which usually (as it is for cfengine enterprise edition) it is
> built
> statically and runs self-governingly from /var/cfengine.
>
> For upstream compability cfengine on OpenBSD has following symlinks:
>
> /var/cfengine/inputs -> ${SYSCONFDIR}/cfengine
> /var/cfengine/bin -> ${LOCALBASE}/sbin
>
> During installation cfengine key was generated in ${CFENGINE_BASE}/ppkeys
> and sample configuration files places in ${SYSCONFDIR}/cfengine to offer
> a user quick start-up with cfengine.
>
> In most of your installations you will only need the cfagent with a proper
> configuration file which would connect to policy hub for its up-to-date
> policies.
>
> For more info you should have a look at the reference manual and the
> relevant
> docs:
>
> http://www.cfengine.org/manuals/cf3-reference.html
>
> cf-report process could be limited by maximum number of openfiles defined
> in
> daemon class, thus consider bumping the openfiles-cur to at least 256 in
> login.conf(5).
Looks nice, this is definitely better than mine..
Kind regards,
Martijn Rijkeboer
