I still think you're making future development/debugging a difficult process,
but I also like the way you're setting things up - it is clean and easy to
understand, and that is _always_ a good thing :-)
-Dan
On Nov 9, 2010, at 2:51 AM, Marc Baudoin wrote:
> Marc Baudoin écrit :
>>
>> As the
Marc Baudoin écrit :
>
> As the number of different types of hosts in my configuration
> grows, I wonder what are the strategies for making bundlesequence
> and inputs more modular.
>
> I define a class for each type of hosts so, of course, there's
> the class approach:
>
> body common control
Bas van der Vlies écrit :
>
> On 9 nov 2010, at 11:32, Marc Baudoin wrote:
>
> > Sure, better than nothing. It works for bundlesequence but not
> > for inputs. I just got this error message:
> >
> > Can't stat file "/var/cfengine/inputs/@(g.inputs)" for parsing
> >
> > Is it possible to use
On 9 nov 2010, at 11:32, Marc Baudoin wrote:
> Michael Potter écrit :
>> On Tue, Nov 9, 2010 at 1:39 AM, Marc Baudoin
>> wrote:
>>>
>>> As the number of different types of hosts in my configuration
>>> grows, I wonder what are the strategies for making bundlesequence
>>> and inputs more modula
Michael Potter écrit :
> On Tue, Nov 9, 2010 at 1:39 AM, Marc Baudoin
> wrote:
> >
> > As the number of different types of hosts in my configuration
> > grows, I wonder what are the strategies for making bundlesequence
> > and inputs more modular.
>
> I have dealt with this topic at length. The
On Tue, Nov 9, 2010 at 1:39 AM, Marc Baudoin
wrote:
> Hi,
>
> As the number of different types of hosts in my configuration
> grows, I wonder what are the strategies for making bundlesequence
> and inputs more modular.
>
> I define a class for each type of hosts so, of course, there's
> the class
On Nov 8, 2010, at 8:02 AM, Marc Baudoin wrote:
> Daniel V. Klein écrit :
>> IMHO, the better strategy is to put everything (common and specific) in the
>> inputs
>
> I'd rather have only what's needed for each type of host instead
> of loading everything.
I know - but I told you what I thoug
Daniel V. Klein écrit :
> IMHO, the better strategy is to put everything (common and specific) in the
> inputs
I'd rather have only what's needed for each type of host instead
of loading everything.
> and then select what is executed in the bundle sequence. But better still is
> to have all t
Hi,
As the number of different types of hosts in my configuration
grows, I wonder what are the strategies for making bundlesequence
and inputs more modular.
I define a class for each type of hosts so, of course, there's
the class approach:
body common control
{
class1::
bundlese
