System overloaded due to a change in the smb.conf
eroseme at emonster.rose.hp.com
Wed Feb 18 21:29:08 GMT 2004
I've seen that twice:
1. smb.conf is huge - 1.5MB (thousands of share defs - solved with %U)
2. useradd script is writing to smb.conf, and blocks all other
processes from reading it
David Collier-Brown wrote:
> Yikes! Samba normally rereads the conf file if it
> detects a change, but it shouldn't be that expensive
> an operation...
> Raphael Berghmans wrote:
>> Samba-3.0.0 with 600 smbd procs.
>> If we make a change in the smb.conf, the system is not available for
>> several minutes (until 15 minutes). Each of 600 smbd process use all the
>> CPU ressource during several seconds.
>> What's happend exactly for each smbd process when a change is made in
>> conf file ?
>> Thank you,
More information about the samba-technical