Sigh, > > Useing daemon(3) instead of fork seems to fix the problem. Of course deamon(3) calls fork, and after a short time I had again the same ktrace output and CPU usage. Martin