I think you want something like:
vars:
any::
'crontab' string => 'foo'; # Set default
redhat::
'crontab' string => 'bar';
suse::
'crontab' string => 'baz';
I don't think you need to bother with negation at all to deal with
this sort of OS-specific data.
You ma
SQLite would be another option to consider. It has quite a bit of
traction now and is actually a pleasure to use. I believe it is also
what the iPhone uses for backend storage. And, it is public domain.
On Tue, Dec 1, 2009 at 2:54 PM, Mark Burgess wrote:
>
>
> Christopher Browne wrote:
>> Mark Bu
On Fri, Dec 11, 2009 at 12:49 PM, Matthias Teege wrote:
> Moin,
>
> > "exists" expression => filesexist("@(filelist)");
>
> I think this only works if the file is on all locations. I'm looking for
> "or".
>
> Many thanks
> Matthias
>
>
So fileexists($(filelist)); is what you need
Nicolas
___
Well, it is still doing it. I think it is the cf-server actually causing the
illegal cipher length in the client. I am using openSSL 0.9.8l. I don't have
the client side dialog, as it is very random on which host does it (and when).
I do have the server debug session from the core dump. Ooops, I
Your email is like the scene in Alice in Wonderland where she is walking down a
corridor
that gets smaller and smaller...the font size seems to disappear into oblivion
with each
line ;-)
Any chance you could capture one of these sessions in debug mode (cut out the
relevant
dialogue)?
My coll
Moin,
> "exists" expression => filesexist("@(filelist)");
I think this only works if the file is on all locations. I'm looking for
"or".
Many thanks
Matthias
___
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listi
Another approach would be:
"exists" expression => filesexist("@(filelist)");
See:
http://www.cfengine.org/manuals/cf3-reference.html#Function-filesexist
Bernd Adamowicz | R&D BasisTechnology
Tel.: +49 (0) 6227 385 332 82 | Fax: +49 (0) 6227 385 588
bernd.adamow...@external.icw-global.com | ww
Hi,
You could try using a list a files :
vars:
"filelist" slist => {"/a/foo", "/b/foo", "/c/foo"};
classes:
"exists" expression => fileexists($(filelist));
Regards,
Nicolas
On Fri, Dec 11, 2009 at 11:39 AM, Matthias Teege wrote:
> Moin,
>
> I can set a class based on the existence of a file w
Moin,
I can set a class based on the existence of a file with fileexists. But
sometimes I have to set a class if a file exists in directory "/a" or
"/b" or "/c". I can use something like this:
"exists_in_a" expression => fileexists("/a/foo");
"exists_in_b" expression => fileexists("/b/foo");
"e
2009/12/11 Mark Burgess :
>
...
> Collecting patterns of data in a simple format is not a bad idea, in the way
> that you
> suggest, then this can be read into an array by cfengine. The key is to make
> the pattern
> itself into a piece of documented system knowledge, not simply use it as a
> sh
This is a technician's point of view. It is only useful to an organization if
it is
clearly documented. The part I was objecting to was the perl script that
generated this
thing, which was a step backwards from comprehensibility.
Collecting patterns of data in a simple format is not a bad idea,
Hi,
Sorry for my sloppy explanation indeed :-)
I have 1 big input file containing lines starting with a host name.
On every host I want to create a separate file from this input file, but it
only contains the lines that need to be present on that host. somthing like
grep $hostname inputfile.txt
2009/12/11 Mark Burgess
>
> Forgive me for pouring scorn on this idea, but it has absolutely no
> conceivable merit to
> use an inappropriately cryptic script to generate something that is supposed
> to be a piece
> of documentation about the system. This is nonsense.
>
Someone could argue that
13 matches
Mail list logo
