I finds the exakt same behaviour on my FreeBSD-server as this mail describes in NetBSD. http://news.gw.com/netbsd.bugs/25829 Is this fixed in -CURRENT and is there some patch that i could patch my 5.1-RELEASE-p10 installation with?