While testing v3.4.32 and and v3.4.33pre1 I've noticed a change in how ipf reacts to 
dupliacte rules in a config-file.
In earlier versions ipf gave an error message like "20:ioctl(add/insert rule): File 
exists" and went on to process next line of config. The newer versions of ipf 
terminate on the first occurance of a duplicate rule (exit(1)).
This means that only config-files that do not contain duplicates get processed 
completely.

Is such a strict behaviour really necessary? 

One shouldn't assume dependence between separate lines in a config-file. Even if a 
line is a duplicate, the others following may very well be correct. The pre-3.4.32 ipf 
seems to work without problems in the presence of duplicate rules.

Alex
begin:vcard 
n:Latour-Henner;Alexander
tel;fax:+46 8 180029
tel;work:+46 70 5954466
x-mozilla-html:FALSE
url:www.servicefactory.com
org:Service Factory AB
version:2.1
email;internet:[EMAIL PROTECTED]
adr;quoted-printable:;;=C5rsta=E4ngsv=E4gen 17, 6tr;Stockholm;;SE-117 43;Sweden
fn:Alex
end:vcard

Reply via email to