High CPU utilization on samba3.0.11

[Peter Tiggerdine]

"Sorry, My crytstal ball is haveing a snow storm" a.k.a
Can you rely with some more details to the problem (ps -auvwx, strace,
etc..)

Harri.Huttula at outokumpu.com wrote:

>Hi,
>
>I have compiled samba3.0.11 + openldap + mit kerberos to aix 5.2 and 
>joined it to AD domain succesfully. All shares works well but soon after 
>smbd is started three samba processes takes 100% CPU utilization. I am not 
>using winbind. Any help would be welcome.
>
>Here is smb.conf
>
>[global]
>        log file = /var/samba/log/log.%m
>        dos charset = 850
>        unix charset = ISO8859-1
>        username map = /usr/local/samba3/lib/user.map.ad
>        encrypt passwords = Yes
>        dns proxy = No
>        nt acl support = No
>        netbios name = Sambaserver1
>        netbios aliases = Sambaserver2
>        browseable = no
>        server string = UNIX Samba server
>        writable = yes
>        password server = kdc1 kdc2 
>        workgroup = ADdomainname
>        realm = AD.DOMAIN.COM
>        security = ADS
>        os level = 20
>        update encrypted = Yes
>        max log size = 50
>        deadtime = 1
>        veto oplock files = /*.dll/*.pbd/*.ini/*.bmp/*.lng/*.exe/*.dwg/
>        socket options = TCP_NODELAY SO_KEEPALIVE
>        preferred master = no
>        local master = no
>        domain master = no
>        log level = 3
>        oplocks = no
>        level2 oplocks = no
>        kernel oplocks = no
>        wins server = wins1 wins1
>        ldap ssl = no
>
>[homes]
>        create mask = 0700
>        directory mode = 0700
>        force directory mode = 0700
>        force create mode = 0700
>        writeable = yes
>        comment = Homes
>        browseable = no
>        valid users = %S
>        veto oplock files = /*.doc/*.xls/*.ppt/
>
>- Harri
>
>
>  
>This message is meant for the addressee only and may contain 
>confidential and legally privileged information. Any unauthorised 
>review, use, copying, storage, disclosure or distribution of this e-
>mail and any attachments is strictly prohibited. If you are not the 
>named recipient or have otherwise received this communication in 
>error, please destroy this message from your system and kindly notify 
>the sender by e-mail. Thank you for your co-operation.
>
>  
>