Re: Stdlib in SCM

Great! But it seems there are still access restrictions when trying to check out using SVN: be...@proxima-centauri:~/THEMEN/EVALUATIONS/Cfengine3> svn co https://svn.iu.hio.no/projects/COPBL/trunk StdLib-trunk Authentication realm: Cfengine AS Password for 'bernd': Au

Fw: Recommended way to get /var/cfengine

Now it works. Some time ago I changed 34 "/var/cfengine/bin" 35 36 comment => "*** Updating files in '/var/cfengine/bin'...", 37 perms => u_p("700"), 38 copy_from => mycopy("/usr/local/sbin","localhost"), to 34 "/var/cfengine/bin" 35 36 comment => "*** Upd

Re: Building cfengine3 on Snow Leopard

Ok. I figured it out. I wasn't pointing to all the required dependencies when configuring... Ultimately the following worked for me ./configure --with-berkeleydb=/usr/local/BerkeleyDB.4.8 --with-openssl=/Users/myuser/local/openssl-0.9.8l --with-pcre=/usr/local/pcre I'm all set now.

Re: copy and file perms

On Mon, Jan 11, 2010 at 07:28:58AM +0100, Mark Burgess wrote: >Neil. You are correct that this option was not implemented. The default value >of all >boolean type /true/false options is always false, so preserving original perms >should not >be the default behaviour. I have patched svn to fix th

Re: Defining Classes in CF-Engine 3

Mark Burgess wrote: Hello Thank you for the very prompt response, would I reference them as "${xyz.ClassName}":: do something Regards Mark. Put the classes in bundle common xyz { } Mark Nelson wrote: Hello I'm not sure how to do this. I want to define

Re: Building cfengine3 on Snow Leopard

Hmm I must be doing something wrong then. I did ./configure, then make and I run into: redner-dev-03:cfengine-3.0.3 root# make Making all in pub gcc -DHAVE_CONFIG_H -I. -I../src -I/usr/include -g -O2 -g -O2 -Wreturn-type -Wmissing-prototypes -Wuninitialized -g -O2 -MT full-write.o -MD -

Re: Defining Classes in CF-Engine 3

No, just xyz:: do something Only classes defined in common classes are global. M Mark Nelson wrote: > Mark Burgess wrote: > > Hello > > Thank you for the very prompt response, would I reference them as > > "${xyz.ClassName}":: > do something > > > Regard

Re: Building cfengine3 on Snow Leopard

Hi Jordan, I might say cfengine3 really supports Snow Leopard. I didn't use MacPorts but compiled all dependencies on my own. Nakarin-MacBook:cfengine-3.0.3 phnakarin$ sw_vers ProductName:Mac OS X ProductVersion: 10.6.2 BuildVersion: 10C540 Nakarin-MacBook:cfengine-3.0.3 phnakarin$ uname

Re: Stdlib in SCM

Thanks for reminding me. Too many things to do. There is now an svn repos for this at http://svn.iu.hio.no/viewvc M bernd.adamow...@external.icw-global.com wrote: > > Happy new year everyone! > > Back from my holidays I started evaluating Cfengine 3.0.3 and of course > the new standard libr

Re: Defining Classes in CF-Engine 3

Put the classes in bundle common xyz { } Mark Nelson wrote: > Hello > > I'm not sure how to do this. I want to define a series of classes at a > single point within the CF-engine configuration and then reference the > classes in various bundles within the CF-Engine configuration system. > >

Defining Classes in CF-Engine 3

Hello I'm not sure how to do this. I want to define a series of classes at a single point within the CF-engine configuration and then reference the classes in various bundles within the CF-Engine configuration system. e.g classes.cf classes: "MailServers"or =>

Re: Building cfengine3 on Snow Leopard

It works. Check your header files Jordan Redner wrote: > Let me re-phrase... > > Is cfengine 3 supported on Snow Leopard? > > > Jordan > > On Jan 8, 2010, at 10:32 AM, Jordan Redner wrote: > >> Are there any links to build cfengine3 on Snow Leopard? >> >> I see that the latest version on M

Re: Building cfengine3 on Snow Leopard

Let me re-phrase... Is cfengine 3 supported on Snow Leopard? Jordan On Jan 8, 2010, at 10:32 AM, Jordan Redner wrote: > Are there any links to build cfengine3 on Snow Leopard? > > I see that the latest version on MacPorts is 2.2. I was successful doing so > on Leopard but make is giving m

Re: Cfengine3 and config file templets

I believe that you can do this now. It works very similar to the expand variables method used in cf2. Sincerely, -- Neil Watson 416-673-3465 CONFIDENTIALITY WARNING This communication, including any attachments, is for the exclusive use of addressee and may contain proprietary and/or confide

Cfengine3 and config file templets

What are some of the approaches for using config file templets with cfengine3 (ie. single sshd_config templet for use with different types of hosts)? Is there any built-in functionality? If not are there plans for any? Thanks, Mahmoud ___ Help-cfe

Re: Recommended way to get /var/cfengine

My mistakes, the path of the files to be copied is wrong, and it does not create the keys, but create the bins. nicolas:/var/#mv cfengine/ cfengine.bak/ nicolas:/var/#mkdir -p /var/cfengine/masterfiles nicolas:/var/#cp /usr/local/share/doc/cfengine/inputs/*.cf /var/cfengine/masterfiles nicolas:/

RE: 3.03 build problem

toheader: Use AC_DEFINE([CFCYG], [], [Description]) autoheader: warning: missing template: MINGW autoreconf: /usr/local/bin/autoheader failed with exit status: 1 (during link) grep: can't open /usr/local/lib/libjpeg.la Can't open /usr/local/lib/libjpeg.la libtool: link: `/usr/local/lib/libjpeg.l

Re: Recommended way to get /var/cfengine

Hi Nicolas, I cannot repoduce this. 'cf-agent --bootstrap' neither copies the binaries nor creates any keys. Both still has to be done manually. Regards Bernd Nicolas Charles wrote on 11.01.2010 15:54:07: > [image removed] > > Re: Recommended way to get /var/cfengine > > Nicolas Charl

Re: Recommended way to get /var/cfengine

bernd.adamow...@external.icw-global.com wrote: > > While (re-)installing 3.0.3 Community I was wondering once again which > is the correct way to get the working directory /var/cfengine. > Obviously it is not created when issuing 'make install' as root. But > when executing 'cf-execd' the first

Recommended way to get /var/cfengine

While (re-)installing 3.0.3 Community I was wondering once again which is the correct way to get the working directory /var/cfengine. Obviously it is not created when issuing 'make install' as root. But when executing 'cf-execd' the first time, the initial structure is created. However, there a

Stdlib in SCM

Happy new year everyone! Back from my holidays I started evaluating Cfengine 3.0.3 and of course the new standard library. Thanks for these improvements! I'd like to suggest to put the standard library under version control. Maybe a directory named 'opt' or 'stdlib' (on the same level as for e