Re: vars defined in agent bundles not usable?

2010-11-16 Thread Daniel V. Klein
There is a bug that has been reported in the latest release involving slists with a single element. I am sure that a patch is on the way soon... -Dan On Nov 16, 2010, at 12:11 PM, Gusto wrote: > Hi Folks, > > I am seeing this behavior on the the 3.1.0 release, where if I define > in a bundle

Re: create file if non-existant

2010-11-16 Thread Michael Potter
You may also want to try using copy_type => "exists" (which is the seed copy), combined with convergent file edits (cfe wont reapply file-edits that are already present. On Wed, Nov 17, 2010 at 7:31 AM, Seva Gluschenko wrote: > for example, > > classes: >    "do_it" not => fileexists("/tmp/foo");

Re: create file if non-existant

2010-11-16 Thread Seva Gluschenko
for example, classes: "do_it" not => fileexists("/tmp/foo"); 2010/11/16 William R. Lorenz : > Hello, > > What's the best method to have cfengine create a file (and do a few > edit_line's on it) without modifying it if it exists?  For example, I > would like cfengine to seed a file but not mod

create file if non-existant

2010-11-16 Thread William R. Lorenz
Hello, What's the best method to have cfengine create a file (and do a few edit_line's on it) without modifying it if it exists? For example, I would like cfengine to seed a file but not modify it again afterwards. I suppose I'm looking for some kind of conditional that might help. Thanks, __

Fwd: vars defined in agent bundles not usable?

2010-11-16 Thread Michael Potter
On Wed, Nov 17, 2010 at 4:11 AM, Gusto wrote: > Hi Folks, > > I am seeing this behavior on the the 3.1.0 release, where if I define > in a bundle some variables I can not use them later on in the same > bundle. The normal order should be vars then later the files right? > This might have been disc

Re: vars defined in agent bundles not usable?

2010-11-16 Thread Seva Gluschenko
Don't mess vars and classes and, perhaps, read the Cfengine reference more thoroughly. Brief rules are: 1. Variables can be accessed outside a bundle by bundle name, e.g. $(bundle_name.variable_name) 2. Lists cannot be accessed outside a bundle directly and should be reinstated locally, e.g. vars

Re: vars defined in agent bundles not usable?

2010-11-16 Thread Gusto
Hi Folks, It would seem that if you have one item in a slist it negates the vars. "master_test" string => "/var/cfmasterfiles/cf310dev/test/"; "master_server" string => "tester.server.com"; Idea was to add more servers as they where defined. Any thoughts? Regards, Gusto On Tue, Nov 16, 2

vars defined in agent bundles not usable?

2010-11-16 Thread Gusto
Hi Folks, I am seeing this behavior on the the 3.1.0 release, where if I define in a bundle some variables I can not use them later on in the same bundle. The normal order should be vars then later the files right? This might have been discussed on another thread that I missed -- tried to follow a

Re: Cfengine Help: Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread Bas van der Vlies
On 16 nov 2010, at 15:02, no-re...@cfengine.com wrote: > Forum: Cfengine Help > Subject: Re: When i process is killed. I want to see the whole process line > instead of only pid. > Author: neilhwatson > Link to topic: https://cfengine.com/forum/read.php?3,19249,19287#msg-19287 > > Might log_str

process_select ttime_range problem (bug)

2010-11-16 Thread Bas van der Vlies
version: cfengine community 3.1.0 os: debian Can somebody confirm this that the calculation of used time of process is wrong. I have have a promise that kills programs that used more then 15 minutes of cpu-time: bundle agent test { vars: any:: "e

Cfengine Help: Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread no-reply
Forum: Cfengine Help Subject: Re: When i process is killed. I want to see the whole process line instead of only pid. Author: neilhwatson Link to topic: https://cfengine.com/forum/read.php?3,19249,19287#msg-19287 Might log_string and log_repair work for you? "The log_string works together with l

Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread Bas van der Vlies
On 16 nov 2010, at 12:44, Seva Gluschenko wrote: > As far as I'm known, the extended information is only available when > you're invoking cf-agent using -I option. There's a reason to submit a > feature request about process_select body for allowance of greater > verbosity, because process number

Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread Seva Gluschenko
As far as I'm known, the extended information is only available when you're invoking cf-agent using -I option. There's a reason to submit a feature request about process_select body for allowance of greater verbosity, because process number is indeed not very informative. 2010/11/16 Bas van der Vl

Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread Bas van der Vlies
On 16-11-10 11:54, Seva Gluschenko wrote: > Bas :) > > just remove action modifier. Warning action means do nothing, just > warn. If you remove the modifier, both warning and signal will be > produced. > Seva, In my first mail "action_policy" was unset and then the following output is produced

Cfengine Help: Reporting bugs

2010-11-16 Thread no-reply
Forum: Cfengine Help Subject: Reporting bugs Author: eystein Link to topic: https://cfengine.com/forum/read.php?3,19282,19282#msg-19282 Hi all, As a reminder, there are detailed (just updated) descriptions on how to report potential bugs in Cfengine at http://www.cfengine.org/pages/troubleshoot.

Re: restart_class

2010-11-16 Thread Michael Potter
On Tue, Nov 16, 2010 at 9:56 PM, Seva Gluschenko wrote: > Michael, > > my observations match yours, restart_class is local to the bundle. > While process_cound body usage can be afforded as a workaround, I > believe you're on the right side to file the bug. Thanks Seva - off to the bugtracker! >

Re: restart_class

2010-11-16 Thread Seva Gluschenko
Michael, my observations match yours, restart_class is local to the bundle. While process_cound body usage can be afforded as a workaround, I believe you're on the right side to file the bug. 2010/11/16 Michael Potter : > The refguide says this about restart class: "A class to be defined > global

Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread Seva Gluschenko
Bas :) just remove action modifier. Warning action means do nothing, just warn. If you remove the modifier, both warning and signal will be produced. 2010/11/16 Bas van der Vlies : > On 15-11-10 15:31, Bas van der Vlies wrote: >> version: cfengine community 3.1.0 >> >> when i process is killed in

restart_class

2010-11-16 Thread Michael Potter
The refguide says this about restart class: "A class to be defined globally if the process is not running..." However, my tests are showing that the class defined with restart class is not defined globally, but local to the bundle. Subsequent bundles that use 'commands' are not able to rely on res

Re: restart_class

2010-11-16 Thread Michael Potter
Hmm seems that using process_select with a body like this: body process_count isnot_running(class) { match_range => irange("1","inf"); out_of_range_define => { "$(class)" }; } Does set a class globally like I expect restart_class to do. On Tue, Nov 16, 2010 at 9:42 PM, Michael Potter wrote: > T

Re: When i process is killed. I want to see the whole process line instead of only pid.

2010-11-16 Thread Bas van der Vlies
On 15-11-10 15:31, Bas van der Vlies wrote: > version: cfengine community 3.1.0 > > when i process is killed in cfengine 3 we only see the pid: > {{{ > cf3 !! Process count for '.*' was out of promised range (1 found) > cf3 I: Made in version '1.2.0' of > '/var/lib/cfengine3/inputs/lisa/quarterly.

Re: reporting bugs via cfengine.com

2010-11-16 Thread Bas van der Vlies
On 15-11-10 22:54, Eystein Måløy Stenberg wrote: > I don't understand your question. The login pages are different: > > *) Support customers can login to https://cfengine.com/otrs/customer.pl > and ask any question they like about Cfengine > (policies/design/architecture/etc.). > > *) Anyone may re