On 2/12/2010 2:04 PM, michoski wrote:
>
> I'm partially to blame for starting it, but I'm honestly not sure where this
> discussion is going...
I'm still trying to get the 1000-foot view of the potential pain/benefit
ratio to expect from cfengine before committing to the effort and
expense of bu
On 2/12/10 8:29 AM, "Les Mikesell" wrote:
> On 2/10/2010 8:30 AM, nwat...@symcor.com wrote:
>> I'm a pretty good perl hacker. I often refer to perl as my Swiss army
>> knife. However, using perl on the scale Cfengine is designed to handle
>> would be difficult. Having to keep a collection of pe
On 2/10/2010 8:30 AM, nwat...@symcor.com wrote:
> I'm a pretty good perl hacker. I often refer to perl as my Swiss army
> knife. However, using perl on the scale Cfengine is designed to handle
> would be difficult. Having to keep a collection of perl modules, and
> dependencies, all at the corre
Les, I think you'll do yourself a service by starting small. Evaluate
Cfengine in small lab. Get a feel for how Cfengine works and how you
manage objects with it. Then you'll be able to better judge how Cfengine
help you.
Sincerely,
--
Neil Watson
416-673-3465
CONFIDENTIALITY WARNING
Thi
On 2/10/2010 1:20 PM, nwat...@symcor.com wrote:
> Moving beyond the hypothetical, Cfengine is a practical solution to
> practical system administration problems. Why don't you describe some
> actual problems that you are facing and how you think Cfengine can help.
> We'll then be able offer our ad
Moving beyond the hypothetical, Cfengine is a practical solution to
practical system administration problems. Why don't you describe some
actual problems that you are facing and how you think Cfengine can help.
We'll then be able offer our advice.
Sincerely,
--
Neil Watson
416-673-3465
CONFI
On 2/10/2010 2:00 AM, Mark Burgess wrote:
>> Can a mostly-uncoordinated
>> set of people write different parts of a cfengine conf without namespace
>> collisions? Is there a way to track internal version dependencies among
>> the parts?
>
> Yes, there are private name spaces in cfengine. Cfengine
I'm a pretty good perl hacker. I often refer to perl as my Swiss army
knife. However, using perl on the scale Cfengine is designed to handle
would be difficult. Having to keep a collection of perl modules, and
dependencies, all at the correct version across dissimilar UNIX platforms,
some of
How about allowing inline body definitions so instead of this (adapted
from the OP):
bundle agent test{
files:
"/root/.ssh/authorized_keys"
create => "true",
perms => m("600");
}
body perms m(mode){
mode => "$(mode)";
}
just write this:
bundle agent test{
files:
> But one thing perl does very well is to allow the number of programmers
> contributing content to scale - which seems to me to be the important
> part if you want to avoid re-inventing every wheel and building things
> from atoms by yourself. The point of using perl is that I can make an
> http
Mark Burgess wrote:
>> It's hard to imagine something that can't be described in perl - or a
>> seasoned sysadmin that doesn't already know how to do it (perhaps badly,
>> but odds are good that 90% of the job can be done with existing CPAN
>> modules...). Suppose you need to work with a proce
> It's hard to imagine something that can't be described in perl - or a
> seasoned sysadmin that doesn't already know how to do it (perhaps badly,
> but odds are good that 90% of the job can be done with existing CPAN
> modules...). Suppose you need to work with a process that exposes its
>
Tuesday, February 09, 2010 3:50 PM
> To: help-cfengine@cfengine.org
> Subject: Re: Directory permissions, and multiple body bundles.
>
> On 2/9/2010 4:23 PM, Justin Lloyd wrote:
>> In a small team of admins, like mine, everyone will need to become a
>> Cfengine admin a
Les, this is what you are looking for, I believe
http://www.cfengine.org/cftimes/articles/21.html
It is a revamp of something we've tried before, but now we have the Cfengine
company
backing up the development, and much improved software.
Cfengine looks different from other languages b
On 2/9/2010 5:28 PM, Justin Lloyd wrote:
> Cfengine 3 is young but I think that with a strong community, over time
> the COPBL will develop into something like what you're describing (or
> something more grassroots could emerge, much like CPAN did).
I don't think CPAN could exist without support f
org
[mailto:help-cfengine-boun...@cfengine.org] On Behalf Of Les Mikesell
Sent: Tuesday, February 09, 2010 3:50 PM
To: help-cfengine@cfengine.org
Subject: Re: Directory permissions, and multiple body bundles.
On 2/9/2010 4:23 PM, Justin Lloyd wrote:
>
> In a small team of admins, like mine,
On 2/9/2010 4:23 PM, Justin Lloyd wrote:
>
> In a small team of admins, like mine, everyone will need to become a
> Cfengine admin and getting people accustomed to a particular model of
> system administration may find the transition to the Cfengine way of
> thinking could be a challenge.
As someo
--
From: help-cfengine-boun...@cfengine.org
[mailto:help-cfengine-boun...@cfengine.org] On Behalf Of Mark Burgess
Sent: Tuesday, February 09, 2010 1:26 PM
To: michoski
Cc: help-cfengine@cfengine.org
Subject: Re: Directory permissions, and multiple body bundles.
You need to study more before making a stat
You need to study more before making a statement like this. It's like saying --
when I
lift the hood of my car I don't like seeing that the engine is complex. You
have no right
to make my engine complex.
I have been trying to encourage people to use a standard set of promise bodies
and *not*
q
On 2/9/10 10:30 AM, "Andrew J. Millar"
wrote:
>> bundle agent test
>> {
>> files:
>> "/root"
>> create => "true",
>> perms => m("700"),
>> file_select => folder(".ssh"),
>> depth_search => recurse("1");
>>
>> "/root/.ssh/authorized_keys"
>> create => "true",
>> perm
If you adapt to using the standard library, then you should not see any of
these "under
the hood" details. This is the way to go forward.
M
Andrew J. Millar wrote:
>> Might be something like this following;
>>
>> bundle agent test
>> {
>> files:
>> "/root"
>> create => "true",
>> per
>
> Might be something like this following;
>
> bundle agent test
> {
> files:
> "/root"
> create => "true",
> perms => m("700"),
> file_select => folder(".ssh"),
> depth_search => recurse("1");
>
> "/root/.ssh/authorized_keys"
> create => "true",
> perms => m("60
On Feb 9, 2010, at 5:55 PM, Andrew J. Millar wrote:
>
>
> If I add in depth_search include_basedir => "true", it changes the permissions
> recursively, which isn't what I want. How can I make this apply only to the
> directory I've specified in the same way it works fine for the authorized_key
>
Hi everyone
I'm struggling with managing permissions of a directory - my aim is to ensure
/root/.ssh has mode 700, but without needing to recurse through it. With a
promise such as the following, cf-agent states
cf3 -> Promise to skip base directory /root/.ssh/.
body common control {
bundleseq
24 matches
Mail list logo
