No, it wasn't answered.
Kind regards,
SebA
-----Original Message----- From: Novosielski, Ryan [mailto:novosirj at umdnj.edu] Sent: 04 October 2012 22:08 To: SebA Cc: xymon; 'Henrik Storner'; 'Dominique Frise'; 'Charles Jones' Subject: Re: [Xymon] depends tag limitations (again)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Was this ever answered? I see I asked the same question again having missed this question just a month prior.
Thanks.
On 09/10/2012 01:17 PM, SebA wrote:
Hi Henrik,
Am I right in thinking that nothing has changed on this front? I just tried to use depends with a custom test and it did not seem to have any effect (on Xymon 4.3.7)...
Dominique Frise wrote:
Hi,
This is an extract of a previous reply from Henrik (http://www.hobbitmon.com/hobbiton/2006/10/msg00141.html):
----------- Henrik Stoerner wrote:
Charles Jones wrote:
*It would be nice if the depend tag worked for any column/test type*. I looked at using the "depends" tag, but it appears that *depends only works for network checks*.
Agreed. The dependency checks are currently implemented in the network test tool (bbtest-net), instead of in the hobbitd daemon - that is the reason why they only work for network tests. And that is purely for historical reasons.
I expect to move all of the dependency code into hobbitd soon, together with the combination-test handling (the stuff currenly done by bbcombotest), that will eliminate this rather silly restriction.
Regards, Henrik
Are the above limitations been removed in the current snapshot? If not when is this going to be implemented?
Thanks.
Dominique UNIL - University of Lausanne
Kind regards,
SebA
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBt+rIACgkQmb+gadEcsb6t+QCgorL/N8IfP24aXalGwElqJ3KC cZcAoNAd3CeAMZgvI0YC6TK4o1mD5DqA =Ku0F -----END PGP SIGNATURE-----