Re: checking for suspicious file names with "suspiciousnames" does not work or am I using it wrong? (3.1.3)

2011-01-31 Thread Eystein Måløy Stenberg
The validation of suspiciousnames was too strict, can you retry svn trunk? -- Regards, Eystein On Tue, Feb 1, 2011 at 6:52 AM, Aleksey Tsalolikhin wrote: > I am getting the same error, "Scalar item in suspiciousnames => { .mo } > in rvalue is out of bounds" under 3.1.4. > > On Mon, Jan 31, 2011

Re: Can Cfengine give me a list of TCP ports that are being listened on? (Like "lsof -i |grep LISTEN" ?)

2011-01-31 Thread Mark Burgess
You can use montoring promises in Nova... On 02/01/2011 08:28 AM, Aleksey Tsalolikhin wrote: > Hi. Three years ago, I wanted to use Cfengine 2 to monitor open ports. > > I wanted to say, "This server A should have ports X, Y and Z open. > If port W is open, it could be an intrusion, so sound t

Can Cfengine give me a list of TCP ports that are being listened on? (Like "lsof -i |grep LISTEN" ?)

2011-01-31 Thread Aleksey Tsalolikhin
Hi. Three years ago, I wanted to use Cfengine 2 to monitor open ports. I wanted to say, "This server A should have ports X, Y and Z open. If port W is open, it could be an intrusion, so sound the alarm." I ended up using ExecResult and an external shell script: (https://cfengine.org/pipermail/he

Re: using a list

2011-01-31 Thread Mark Burgess
Sandra, I think what you want to do is include one list in another. In that case you must refer to the list as @(variable). By writing $(variable) you are asking Cfengine to iterate the promise multiple times FOREACH value in @(variable), defining multiple conflicting access promises. See ht

Re: checking for suspicious file names with "suspiciousnames" does not work or am I using it wrong? (3.1.3)

2011-01-31 Thread Aleksey Tsalolikhin
I am getting the same error, "Scalar item in suspiciousnames => { .mo } in rvalue is out of bounds" under 3.1.4. On Mon, Jan 31, 2011 at 10:35 AM, Aleksey Tsalolikhin wrote: > Hi.  I'm trying to implement suspiciousnames check as per > http://www.cfengine.org/manuals/cf3-reference.html#suspicious

Cfengine Help: Re: Cfengine 3.1.4 is released

2011-01-31 Thread no-reply
Forum: Cfengine Help Subject: Re: Cfengine 3.1.4 is released Author: debheller Link to topic: https://cfengine.com/forum/read.php?3,20344,20345#msg-20345 That's GREAT news! When will the Nova update be released? ___ Help-cfengine mailing list Help-cf

Re: using a list

2011-01-31 Thread Nicolas Charles
Hello, I'm not sure you can use a vars section in a bundle server I would suggest that you define a bundle common, and define your list there, and use it in your server control and access_rules, like : bundle common my_definitions { vars: "sdm_host_list" slist => { "255.3.30.102", "255.3.30.43"

using a list

2011-01-31 Thread Sandra Wittenbrock
Hello, I am trying to use a list of servers, so I don't have to enter the servers individually. Unfortunately, the variable sdm_host_list is not working for me. Any pointers would be appreciated. Currently I have in serverd.cf: body server control { allowallconnects=> {

Re: How to check out cfengine source?

2011-01-31 Thread Erlend Leganger
On 31 January 2011 21:29, Aleksey Tsalolikhin wrote: > I do not have a solution for this, I hope you got along OK with the > tarball generator? > Well, I had some problems compiling from the tarball generator for svn 1717, but that seems to be fixed now (at least the make clean; make; make insta

Re: Cfengine Help: Re: importing tasks based on host group

2011-01-31 Thread Seva Gluschenko
Brad, there are at least two errors in your setup. First, common bundles aren't to be included into the bundlesequence. Next, inputs is the only way to specify input files. So that, your current setup is meaningless. You can achieve some distinction using classes, e.g. body common control { lin

RE: A couple of questions about cf_Audit.db

2011-01-31 Thread Simon Oxwell
Mark, Thank you for the advice! Simon -Original Message- From: help-cfengine-boun...@cfengine.org [mailto:help-cfengine-boun...@cfengine.org] On Behalf Of Mark Burgess Sent: 17 January 2011 10:52 To: help-cfengine@cfengine.org Subject: Re: A couple of questions about cf_Audit.db Simon

Cfengine Help: Cfengine 3.1.4 is released

2011-01-31 Thread no-reply
Forum: Cfengine Help Subject: Cfengine 3.1.4 is released Author: eystein Link to topic: https://cfengine.com/forum/read.php?3,20344,20344#msg-20344 Cfengine 3.1.4 is released - a bugfix release The 3.1.4 release fixes some urgent bugs that were discovered just after the 3.1.3 release. One featur

Re: v3.1.4 due out?

2011-01-31 Thread Eystein Måløy Stenberg
About 10 minutes. :) --Eystein On 01/31/2011 09:35 PM, JIM AMANATIDIS, BLOOMBERG/ 731 LEXIN wrote: > Saw the other day that v3.1.4 may be due out soon? Just curious if there is > an ETA, thanks, Jim > ___ > Help-cfengine mailing list > Help-cfengine@cf

v3.1.4 due out?

2011-01-31 Thread JIM AMANATIDIS, BLOOMBERG/ 731 LEXIN
Saw the other day that v3.1.4 may be due out soon? Just curious if there is an ETA, thanks, Jim ___ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine

Re: Cfengine Help: Re: importing tasks based on host group

2011-01-31 Thread Brad Huntington
Still a little confused. Can someone please point me in the right direction here, I"m not sure why the linux tasks don't get executed. ## # # promises.cf # #

checking for suspicious file names with "suspiciousnames" does not work or am I using it wrong? (3.1.3)

2011-01-31 Thread Aleksey Tsalolikhin
Hi. I'm trying to implement suspiciousnames check as per http://www.cfengine.org/manuals/cf3-reference.html#suspiciousnames-in-agent but it ain't going: [cfengine00 cfengine]# cat ./test_aleksey.cf body common control { bundlesequence => { "report_suspicious_file_names" }; } body agent control

FOSDEM 2011 - Configuration & Systems Management

2011-01-31 Thread Nicolas Charles
Hi, The Fosdem (http://fosdem.org/2011/) is this week-end, at Brussels, Belgium, and Sunday will be an exciting day for anyone interested with Configuration & Systems Management : a room is reserved for talk exclusively on this subject fro the whole day. For those brave enough to be awake at 9