On Thu, Sep 6, 2012 at 7:05 PM, Diego Zamboni wrote:
> It seems there's a good set of valid use cases for this - would someone care
> to open a feature request for it? Please use the tracker at
> https://cfengine.com/dev/projects/core
>
Here is https://cfengine.com/dev/issues/1112
_
trying to setup cfengine on my network and faced unexpected behavior.
>>> Most of my linux nodes have routable IPs defined under lo interface,
>>> like 192.168.1.5/32 192.168.78.25/32 and so on,
>>> but looks like cfengine doesn't define class with the IPs of the
>>
st of my linux nodes have routable IPs defined under lo interface,
> > like 192.168.1.5/32 192.168.78.25/32 and so on,
> > but looks like cfengine doesn't define class with the IPs of the
> > loopback interface. Is it intended behaviour, if so, why ?
> > Then running /va
sei Sheshka wrote:
>
>> Hi list!
>>
>> I'm trying to setup cfengine on my network and faced unexpected behavior.
>> Most of my linux nodes have routable IPs defined under lo interface,
>> like 192.168.1.5/32 192.168.78.25/32 and so on,
>> but looks like cfen
2012, at 9:58 AM, Aliaksei Sheshka wrote:
> Hi list!
>
> I'm trying to setup cfengine on my network and faced unexpected behavior.
> Most of my linux nodes have routable IPs defined under lo interface,
> like 192.168.1.5/32 192.168.78.25/32 and so on,
> but looks like cfengi
Hi list!
I'm trying to setup cfengine on my network and faced unexpected behavior.
Most of my linux nodes have routable IPs defined under lo interface,
like 192.168.1.5/32 192.168.78.25/32 and so on,
but looks like cfengine doesn't define class with the IPs of the
loopback interf
