Hi,
Yes, we should keep only the 2nd version. We should use notification output
in the future, but it will be with a fill test code, so drop it, when we
will really need it, we will add it.
And thanks for the TAB->4SP patch ;)
Jean
2011/1/2 Grégory Starck <g.sta...@gmail.com>
> class Notification(Action):
>
> @ line 184:
> def get_return_from(self, c):
> self.exit_status = c.exit_status
> self.output = c.output
>
> ...
>
> @ line 226:
> def get_return_from(self, n):
> self.exit_status = n.exit_status
>
>
> I guess it's the second one that's actually being used.
>
> first one is so like "hidden" and could/should be removed, wdyt ?
>
> greg.
>
>
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
