On 05/18/2011 01:11 PM, Jochen Bern wrote:
> On 05/18/2011 12:09 PM, Andreas Ericsson wrote:
>> A service that returns OK when its parent has returned non-OK is
>> obviously misconfigured (since it really shouldn't be ok with a non-OK
>> parent)
>
> Probably just a tangent, but I strongly disagree
On 05/17/2011 02:14 PM, lists wrote:
> You can probally ask these questions your self but...
> If my understanding of this is correct, How will this work in a
> templated environment?
> eg Will the parent service be configured via a hostname / service name pair
> Or just a service name, that Nagios
On 05/17/2011 11:53 AM, Max Schubert wrote:
> On Tue, May 17, 2011 at 5:48 AM, Andreas Ericsson wrote:
>> On 05/17/2011 11:34 AM, Max Schubert wrote:
>>> Andreas,
>>>
>>> How does this differ functionality from the current ability to
>>> describe dependencies with servicedependency? Is it just ea
On Tue, May 17, 2011 at 5:48 AM, Andreas Ericsson wrote:
> On 05/17/2011 11:34 AM, Max Schubert wrote:
>> Andreas,
>>
>> How does this differ functionality from the current ability to
>> describe dependencies with servicedependency? Is it just easier to
>> define (I agree that would be a win)
>>
On 05/17/2011 11:34 AM, Max Schubert wrote:
> Andreas,
>
> How does this differ functionality from the current ability to
> describe dependencies with servicedependency? Is it just easier to
> define (I agree that would be a win)
>
It's just easier to describe, and it ties in nicely with differ
Andreas,
How does this differ functionality from the current ability to
describe dependencies with servicedependency? Is it just easier to
define (I agree that would be a win)
--
Achieve unprecedented app performance and
