rules.xml and <memsize> parameter
I am unable to get my memsize rules working properly. It states in the documentation that the memsize is recognized in megabytes, but that doesn't seem to be the case. Every value I use for memsize seems to match any system, until I get to 10000000000000000000 or greater. In other words, with the below rules.xml, the first rule matches all systems(which is what I want so that every system uses the default.xml file). However, all systems match the next two rules as well, so that all 3 xml files are merged. But I only want the first rule file and one of the 2 next rules files merged based on memory being either less than 3000MB or greater than 3000MB. So I end up getting a merged rules file of all 3. I copied the syntax directly from the example in the autoyast guide. Is there a bug in the memsize option? I am using the below rules.xml file..... <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <memsize> <match>128</match> <match_type>greater</match_type> </memsize> <result> <profile>default.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>cciss.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>3000</match> <match_type>greater</match_type> </memsize> <result> <profile>cciss4g.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>5000</match> <match_type>greater</match_type> </memsize> <result> <profile>cciss6g.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall>
On Tuesday 13 September 2005 15:23, Reynold L Demarco wrote:
I am unable to get my memsize rules working properly. It states in the documentation that the memsize is recognized in megabytes, but that doesn't seem to be the case. Every value I use for memsize seems to match any system, until I get to 10000000000000000000 or greater. In
which version of SUSE Linux do you use? Your example is working fine here on a SUSE Linux 10.0 It would also be interesting to see what's in /var/log/YaST2/y2log. Search for "Bash return" in that file. SUSE Linux 10.0 will have a tool in the installation system that can print out all values of all possible rule keys. For example, it shows 1024 for memsize on my test system (which is correct for 1GB RAM). If I change the value to 1024 in the rules.xml you provided, the default.xml is not fetched here. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
I am finding the issue in SLES9 SP2. Hmm, could it be a bug in SLES9 maybe? Uwe Gansert wrote:
On Tuesday 13 September 2005 15:23, Reynold L Demarco wrote:
I am unable to get my memsize rules working properly. It states in the documentation that the memsize is recognized in megabytes, but that doesn't seem to be the case. Every value I use for memsize seems to match any system, until I get to 10000000000000000000 or greater. In
which version of SUSE Linux do you use? Your example is working fine here on a SUSE Linux 10.0 It would also be interesting to see what's in /var/log/YaST2/y2log. Search for "Bash return" in that file.
SUSE Linux 10.0 will have a tool in the installation system that can print out all values of all possible rule keys. For example, it shows 1024 for memsize on my test system (which is correct for 1GB RAM).
If I change the value to 1024 in the rules.xml you provided, the default.xml is not fetched here.
On Tuesday 13 September 2005 16:54, Reynold L Demarco wrote:
I am finding the issue in SLES9 SP2. Hmm, could it be a bug in SLES9 maybe?
I don't think so. I just tried it on a SLES9 SP2 too and it's working fine there. With memsize 128 the default.xml gets fetched. With memsize 1024 it's not getting fetched (I have a 1GB machine). The other xml files are never fetched, because I don't have the devices you have in your profile. So the rules can't match. You have to take a look into the y2log, Maybe there is some information. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Ok, I'm taking a look now at y2log. But what I'm finding is that default.xml always gets retrieved. And it is merged with the others whether I have 1GB,2GB,3GB memory or not. I'm going to do another run so I can get a good y2log. The only y2log I have currently is my last attempt when I set the vaules real high so that it finally didn't match . Uwe Gansert wrote:
On Tuesday 13 September 2005 16:54, Reynold L Demarco wrote:
I am finding the issue in SLES9 SP2. Hmm, could it be a bug in SLES9 maybe?
I don't think so. I just tried it on a SLES9 SP2 too and it's working fine there. With memsize 128 the default.xml gets fetched. With memsize 1024 it's not getting fetched (I have a 1GB machine). The other xml files are never fetched, because I don't have the devices you have in your profile. So the rules can't match.
You have to take a look into the y2log, Maybe there is some information.
On Tuesday 13 September 2005 17:38, Reynold L Demarco wrote:
Ok, I'm taking a look now at y2log. But what I'm finding is that default.xml always gets retrieved. And it is merged with the others whether I have 1GB,2GB,3GB memory or not.
I'm interested in the "Bash return" lines. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Ok, here's my log during the install after it parses the rules.xml file...In this case, you'll see my system has 3584MB of memory, yet its pulling the rules files for matching at greater than 3000 and 5000 memsize... 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$memsize" -gt "128" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: default.xml 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:395 var: 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["disksize_device0":"/dev/cciss/c0d0", "disksize_device1":"/dev/cciss/c1d0", "disksize_device2":"/dev/cciss/c2d0", "disksize_device3":"/dev/cciss/c3d0", "disksize_device4":"/dev/evms", "disksize_size0":34727, "disksize_size1":2097151, "disksize_size2":2097151, "disksize_size3":2097151, "disksize_size4":0, "memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: cciss.xml 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:395 var: 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" -a "$memsize" -gt "3000" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["disksize_device0":"/dev/cciss/c0d0", "disksize_device1":"/dev/cciss/c1d0", "disksize_device2":"/dev/cciss/c2d0", "disksize_device3":"/dev/cciss/c3d0", "disksize_device4":"/dev/evms", "disksize_size0":34727, "disksize_size1":2097151, "disksize_size2":2097151, "disksize_size3":2097151, "disksize_size4":0, "memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: cciss4g.xml 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:395 var: 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" -a "$memsize" -gt "5000" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["disksize_device0":"/dev/cciss/c0d0", "disksize_device1":"/dev/cciss/c1d0", "disksize_device2":"/dev/cciss/c2d0", "disksize_device3":"/dev/cciss/c3d0", "disksize_device4":"/dev/evms", "disksize_size0":34727, "disksize_size1":2097151, "disksize_size2":2097151, "disksize_size3":2097151, "disksize_size4":0, "memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: cciss6g.xml 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:395 var: 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:627 Getting Rules: ["default.xml", "cciss.xml", "cciss4g.xml", "cciss6g.xml"] Uwe Gansert wrote:
On Tuesday 13 September 2005 17:38, Reynold L Demarco wrote:
Ok, I'm taking a look now at y2log. But what I'm finding is that default.xml always gets retrieved. And it is merged with the others whether I have 1GB,2GB,3GB memory or not.
I'm interested in the "Bash return" lines.
On Tuesday 13 September 2005 17:58, Reynold L Demarco wrote:
Ok, here's my log during the install after it parses the rules.xml file...In this case, you'll see my system has 3584MB of memory, yet its pulling the rules files for matching at greater than 3000 and 5000 memsize...
2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$memsize" -gt "128" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: default.xml
this looks good to me and if you set the memsize rule to at least 3584, it should not fetch default.xml. Since it always fetches the default.xml, I'm a bit confused. Maybe you can strip the rules.xml file down to just the first rule with the memsize and play around with memsize=128 and memsize=4000. If both cases work, then we can insert more rules. If not, we have to start to debug that first rule. I'll take a closer look at this tomorrow. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Ok, I'll give that a shot. Thx Uwe Gansert wrote:
On Tuesday 13 September 2005 17:58, Reynold L Demarco wrote:
Ok, here's my log during the install after it parses the rules.xml file...In this case, you'll see my system has 3584MB of memory, yet its pulling the rules files for matching at greater than 3000 and 5000 memsize...
2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$memsize" -gt "128" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: default.xml
this looks good to me and if you set the memsize rule to at least 3584, it should not fetch default.xml. Since it always fetches the default.xml, I'm a bit confused. Maybe you can strip the rules.xml file down to just the first rule with the memsize and play around with memsize=128 and memsize=4000. If both cases work, then we can insert more rules. If not, we have to start to debug that first rule.
I'll take a closer look at this tomorrow.
Ok, here's my log during the install after it parses the rules.xml file...In this case, you'll see my system has 3584MB of memory, yet its pulling the rules files for matching at greater than 3000 and 5000 memsize...
and there's the problem, right there:
2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" -a "$memsize" -gt "5000" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["disksize_device0":"/dev/cciss/c0d0", "disksize_device1":"/dev/cciss/c1d0", "disksize_device2":"/dev/cciss/c2d0", "disksize_device3":"/dev/cciss/c3d0", "disksize_device4":"/dev/evms", "disksize_size0":34727, "disksize_size1":2097151, "disksize_size2":2097151, "disksize_size3":2097151, "disksize_size4":0, "memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: cciss6g.xml
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). The bash test should be: if [ \( "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" \) -a "$memsize" -gt "5000" ]; then exit 0; else exit 1; fi The key being the '\(' & '\)' pair. I reported this to Novell as a bug in SLES9 back in October (i.e. almost a year ago). I would have thought that the fix would have been incorporated by SP2.
Thanks Joe, I thought I was going crazy with this. This is definitely the behavior I've found as well. Individual rules work fine, combined rules are an issue. Joseph V Moss wrote:
Ok, here's my log during the install after it parses the rules.xml file...In this case, you'll see my system has 3584MB of memory, yet its pulling the rules files for matching at greater than 3000 and 5000 memsize...
and there's the problem, right there:
2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:375 Bash return: if [ "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" -a "$memsize" -gt "5000" ]; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["disksize_device0":"/dev/cciss/c0d0", "disksize_device1":"/dev/cciss/c1d0", "disksize_device2":"/dev/cciss/c2d0", "disksize_device3":"/dev/cciss/c3d0", "disksize_device4":"/dev/evms", "disksize_size0":34727, "disksize_size1":2097151, "disksize_size2":2097151, "disksize_size3":2097151, "disksize_size4":0, "memsize":3584]) 2005-09-13 15:48:26 <1> linux(722) [YCP] AutoInstallRules.ycp:382 file: cciss6g.xml
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). The bash test should be:
if [ \( "$disksize_size0" -gt "1000" -a "$disksize_device0" = "/dev/cciss/c0d0" -o "$disksize_size1" -gt "1000" -a "$disksize_device1" = "/dev/cciss/c0d0" -o "$disksize_size2" -gt "1000" -a "$disksize_device2" = "/dev/cciss/c0d0" -o "$disksize_size3" -gt "1000" -a "$disksize_device3" = "/dev/cciss/c0d0" -o "$disksize_size4" -gt "1000" -a "$disksize_device4" = "/dev/cciss/c0d0" \) -a "$memsize" -gt "5000" ]; then exit 0; else exit 1; fi
The key being the '\(' & '\)' pair. I reported this to Novell as a bug in SLES9 back in October (i.e. almost a year ago). I would have thought that the fix would have been incorporated by SP2.
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. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
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.
On Tuesday 13 September 2005 20:33, Joseph V Moss wrote:
I would have thought that the fix would have been incorporated by SP2.
BTW, I just took a closer look at the code and this is(!) fixed in SP2. I did a complete test, including disksize rules, by myself and it is working fine here. So, I can't say why it's not working for Reynold. I tried the following rule set and 1.xml + 2.xml are fetched. 3.xml is not on a SLES9 SP2. The shell script that handles the rule looks good. The disksize and memsize check are seperated in two different tests. Reynold, please add Y2DEBUG=1 to your linuxrc parameter list and send me the y2log via eMail (not to the list, it's too huge for the mailinglist). <rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>1.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>1000</match> <match_type>greater</match_type> </memsize> <result> <profile>2.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>5000</match> <match_type>greater</match_type> </memsize> <result> <profile>3.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Ok, I will give the below a shot. Won't get to it today, but I will try it over the weekend. I was trying this on SP2. For now I got it working by using separate rules and just putting my rules in the correct order so the files are merged properly. Thanks, Renny Uwe Gansert wrote:
On Tuesday 13 September 2005 20:33, Joseph V Moss wrote:
I would have thought that the fix would have been incorporated by SP2.
BTW, I just took a closer look at the code and this is(!) fixed in SP2. I did a complete test, including disksize rules, by myself and it is working fine here. So, I can't say why it's not working for Reynold. I tried the following rule set and 1.xml + 2.xml are fetched. 3.xml is not on a SLES9 SP2. The shell script that handles the rule looks good. The disksize and memsize check are seperated in two different tests.
Reynold, please add Y2DEBUG=1 to your linuxrc parameter list and send me the y2log via eMail (not to the list, it's too huge for the mailinglist).
<rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>1.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>1000</match> <match_type>greater</match_type> </memsize> <result> <profile>2.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>5000</match> <match_type>greater</match_type> </memsize> <result> <profile>3.xml</profile> <continue config:type="boolean">true</continue> </result> </rule>
Do you know the complete list of conditions? I only know greater because that's in the examples. E.g. is is it less, equal, etc? Uwe Gansert wrote:
On Tuesday 13 September 2005 16:54, Reynold L Demarco wrote:
I am finding the issue in SLES9 SP2. Hmm, could it be a bug in SLES9 maybe?
I don't think so. I just tried it on a SLES9 SP2 too and it's working fine there. With memsize 128 the default.xml gets fetched. With memsize 1024 it's not getting fetched (I have a 1GB machine). The other xml files are never fetched, because I don't have the devices you have in your profile. So the rules can't match.
You have to take a look into the y2log, Maybe there is some information.
On Tuesday 13 September 2005 17:43, Reynold L Demarco wrote:
Do you know the complete list of conditions? I only know greater because that's in the examples. E.g. is is it less, equal, etc?
exact,greater,lower,range the default is exact. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (3)
-
Joseph V Moss -
Reynold L Demarco -
Uwe Gansert