We had a case where an early release cfengine (I think 3.0.2b1)
was running but not updating file on clients. I believe the problem
here is a cf-server that's horked and we'll be upgrading this soon
but it raised the question; How do you monitor cfengine? Obviously
cfengine shouldn't monitor itself
Thanks, that got me further. It required a few more dependancies
including bison and flex. It now runs configure fine and most(?)
of the make but fails at OpenDB with a warning about dbp.
I'm getting a similar error as listed in
https://cfengine.org/pipermail/help-cfengine/2009-June/005534.htm
I compiled cfengine 3.0.2 on a Suse 10.2 box without any problem. This
machine is my server and is working fine as are most of the clients. One
of my clients is SLES 11.0 Altho it's the same architecture, I figured I
either need to or at least should recompile on this box. I've installed
BerkeleyDB
