On 2013/03/23 14:10, Martijn Rijkeboer wrote:
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...
Here's an updated diff including a reworked README.
I removed cf_serverd from the cfengine rc
And this is normal?
# /etc/rc.d/cfengine -d start
doing rc_read_runfile
usage: /etc/rc.d/cf_execd [-df] {start|check|reload|restart|stop}
doing rc_read_runfile
usage: /etc/rc.d/cf_serverd [-df] {start|check|reload|restart|stop}
doing rc_read_runfile
usage: /etc/rc.d/cf_monitord [-df]
On Tue, Mar 19, 2013 at 11:46:06AM +, Stuart Henderson wrote:
| 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
| 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
On 2013/03/19 12:22, Martijn Rijkeboer wrote:
| 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/*
Updated to 3.4.4...
@sample files based on NetBSD port, mandatory is promises.cf,
failsafe.cf if promises.cf not found. promises.cf tries to
load other files... This is OK for local agent.
1 @sample ${CFENGINE_BASE}/
2 @sample ${CFENGINE_BASE}/masterfiles/
3 @sample
Penned by Martijn Rijkeboer on 20130316 8:20.50, we have:
| Hi,
|
| The attached archive is take 3 of an update of sysutils/cfengine to version
| 3.4.2. This version explicitly disables libvirt because when libvirt was
| installed it was build with libvirt.
|
| I've chosen to disable libvirt
On Mon, Mar 18, 2013 at 09:33:55AM -0500, Todd T. Fries wrote:
As I pointed out to the libvirt maintainer, libvirt should be enabled to use
the qemu engine that does work on OpenBSD.
Sure it is slower than real hardware, and because of this it makes little
sense
to use for more than
As I pointed out to the libvirt maintainer, libvirt should be enabled to
use the qemu engine that does work on OpenBSD.
Sure it is slower than real hardware, and because of this it makes
little sense to use for more than testing, but personally I find
having a test network of qemu instances
Penned by Martijn Rijkeboer on 20130318 13:12.18, we have:
| As I pointed out to the libvirt maintainer, libvirt should be enabled to
| use the qemu engine that does work on OpenBSD.
|
| Sure it is slower than real hardware, and because of this it makes
| little sense to use for more than
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.
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
Hi,
The attached archive is take 3 of an update of sysutils/cfengine to version
3.4.2. This version explicitly disables libvirt because when libvirt was
installed it was build with libvirt.
I've chosen to disable libvirt because, to my knowledge, OpenBSD can't be
used as a (production) host for
13 matches
Mail list logo
