Heya,
the growing number of smbd process and therewith the resulting 100% cpu usage have their reason in samba not killing processes which are not used anymore (since every client causes Samba to spawn a new process).
You can resolve this issue by putting
deadtime = 60
into your smb.conf. This causes Samba to kill processes which are not used anymore after 60 minutes which should be sufficient.
Hope I helped!
Have a nice day,
Ulrik
Matthias Henze wrote:
hi,
i've a debian sarge setup with samba 3.0.10 with ldap as SAM backend. every thing used to work as expected, but last week the machine went down. an analysis of the problem has showen, that with increasing uptime there is a growing number of smbd processes that caus 100% CPU utilation. tests have showen, that i can kill these processes without harming smb conecctivtiy. this is a workaround but no soulution.
i've absolutely no idea what causes this and what i can/should do to track this down.
any suggestions ?
TIA
Matthias Henze [EMAIL PROTECTED]
Use PGP!! http://www.mhcsoftware.de/MatthiasHenze.asc - - - - - - - - - - - - - - - - - - - - - - - - - - - MHC SoftWare GmbH voice: +49-(0)9533-92006-0 Fichtera 17 fax: +49-(0)9533-92006-6 96274 Itzgrund/Germany e-Mail: [EMAIL PROTECTED] - - - - - - - - - - - - - - - - - - - - - - - - - - -
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
