Cfengine Help: Re: Package architecture specification being ignored by cf3

2011-01-26 Thread no-reply
Forum: Cfengine Help Subject: Re: Package architecture specification being ignored by cf3 Author: eystein Link to topic: https://cfengine.com/forum/read.php?3,17577,20291#msg-20291 This was indeed a bug, see the status here: https://cfengine.com/bugtracker/view.php?id=456 A patch has been submitt

Cfengine Help: Re: cf_lastseen adding old key?

2011-01-26 Thread no-reply
Forum: Cfengine Help Subject: Re: cf_lastseen adding old key? Author: matter Link to topic: https://cfengine.com/forum/read.php?3,20285,20292#msg-20292 So I am not so crazy, I did find a bug when cf-agent checks the keys. Consider the following cf-agent output: cf3 No existing connection to 10.

Cfengine Help: Re: cf_lastseen adding old key?

2011-01-26 Thread no-reply
Forum: Cfengine Help Subject: Re: cf_lastseen adding old key? Author: mark Link to topic: https://cfengine.com/forum/read.php?3,20285,20293#msg-20293 I wonder why the strncmp was used in the first place? It looks like it should just be strcmp() rather than strncmp() _

Versions of dependencies for building 3.1.3?

2011-01-26 Thread Mike Svoboda
Hey folks I was trying to get an idea / might be cool to include in the release notes the versions of dependencies that people have had success running 3.1.3 on. (pcre, openssl, berkeleydb, flex, etc.) I’m running into a weird issue where my x86 hosts aren’t having any issue with 3.1.3 runnin

Re: Versions of dependencies for building 3.1.3?

2011-01-26 Thread Mark Burgess
Mike, with sincere apologies, this is a bug in 3.1.3 already fixed in svn, and 3.1.4 is forthcoming within a few days. Mark On 01/26/2011 06:23 PM, Mike Svoboda wrote: > Hey folks > > I was trying to get an idea / might be cool to include in the release > notes the versions of dependencies tha

cf-execd.cf mailto

2011-01-26 Thread tktucker
Is it possible to define multiple recipients on the mailto line? My testing with "user@domain[delimeter]user2@domain" separated with spaces, commas and semicolons have been unsuccessful. ___ Help-cfengine mailing list Help-cfengine@cfengine.org https:/