I should cvsup to latest RELENG_5_2 and try this out. > current is current ... it's no problem to fix it later... but what about > release 5.2.1-rc2 ? which suffers from same problem ? >