Yes, I tested just memsize, and it works as I would expect it to with just one rule per condition. In the case of the memsize being greater than 128, it always was in my case, so it always grabbed default.xml. Along with whatever other conditions were met as single rules. Uwe Gansert wrote:
On Tuesday 13 September 2005 20:33, Joseph V Moss wrote:
and there's the problem, right there:
It has nothing to do with memsize checking. The problem is that multiple conditions within a single rule aren't handled properly (or at least not when one of the conditions is a <disksize> condition).
and that's what I saw yesterday evening too. That's why I wanted Reynold to test just the memsize option because my tests of multiple conditions on the command line did not look too well too and I expected a bug there. But Reynold wrote that even the default.xml from the single memsize rule matched always. That did not (and still don't) fit into the picture of the bug I had.
The bash test should be:
thanks. You saved me some time digging. I'll fix that.