We have a problem with our samba-2.2.5 PDC looping against our ldap server. The smbd process consumes more and more memory until the system runs out or until we kill it. The smbd is not the core process, but a child which is handling a Windows XP user session. There is no output from the smbd process if I switch on level 10 debugging using smbcontrol. I don't know if this is because the smbd is in such a hard loop that it does not respond to the signal or that the loop does not include any debug statements. The smbd cannot be killed by kill -TERM, it has to be a kill -9. If I use par on the process it is looping around a select() and a read(). The system is handling hundreds of concurrent XP user sessions which look Ok, but several times a day we have one of these run-away processes. We have switched on logging of the ldap, but there is so much activity from all the normal sessions that we can't see what the run-away activity is. Any ideas please? Phil. --------------------------------------- Phil Chambers (postmaster@exeter.ac.uk) University of Exeter