<html><head><style type="text/css"></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:12pt"><br><font size="3"><span style="font-family: courier,monaco,monospace,sans-serif;"></span></font><div style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">Från:</span></b> Ton Voon <tonvoon@gmail.com><br><b><span style="font-weight: bold;">Till:</span></b> Nagios Developers List <nagios-devel@lists.sourceforge.net><br><b><span style="font-weight: bold;">Skickat:</span></b> tis 9 november 2010 10:41:14<br><b><span style="font-weight: bold;">Ämne:</span></b> Re: [Nagios-devel] Empty host/service-group patch<br></font><br><meta http-equiv="x-dns-prefetch-control" content="off"><br><div><div>On 8 Nov 2010, at 23:04, Sven-Göran Bergh wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><div><div style="margin: 0px; font-family: courier,monaco,monospace,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">a small patch that stomps down a bug in parsing<br>empty host/service-groups.<br></div></div></span></blockquote><div><br></div>Nasty! Can you update the test configurations to trigger this bug? Then with your patch we should see that the problem is fixed.</div><div><br></div><div>Details on tests here: <a rel="nofollow" target="_blank" href="http://wiki.nagios.org/index.php/Nagios_Core_Developer_Guidelines#Testing">http://wiki.nagios.org/index.php/Nagios_Core_Developer_Guidelines#Testing</a></div><div><br></div><div>Ton</div><div><br><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">The first time I saw this was in version 3.2.0 and<br></span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">I have not been able to isolate it until now.</span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> It has a<br>true random behaviour. The result depends on first<br>"poluting" the right memory with previous configs. Thus<br>I am not sure that a positive test on one platfrom may<br>be repeated elseware. I have a small config file that<br>works for me, but I am not sure it will fail on other<br>archs.<br><br><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Anyway, I will try to produce a test that triggers it,</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">but it will probably not be a 100% proof trigger.</span></span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">/S-G</span><br><br></div><meta http-equiv="x-dns-prefetch-control" content="on"></div></div> </div><br></body></html>