[Samba] When to restart samba

[Andrew Masterson]

> > If I understand correctly, in order to have the smb.conf file
applied
> > you need to restart smbd.
> >
> > Is "service smbd reload" sufficient (which does a "killproc smbd
-HUP")?
> > Will this kill any active connections to samba resources causing
user
> > disruption?  Or is this a seamless process that can be carried out
> > midday?
> >
> > I ask because if I need to kill all user connections to production
> > shares in order to test different share parameters that changes my
> > approach.
> 
> If you make changes to the [global] stanza in smb.conf you need to
restart
> Samba's smbd and nmbd daemons.

And winbind as well?  The documentation seems to indicate that winbindd
needs to be started after nmbd and smbd - so does it need to be
restarted as well, or will it remain active?  Are there potential
conflicts if winbind isn't shut down before restarting the nmbd and smbd
daemons?

> Changes to the share stanzas in smb.conf generally do not require a
> restart of smbd. Smbd monitors the smb.conf file for changes.

Could you elaborate on "generally" and give me an estimate of how long
it takes for the changes to be reloaded?

Thanks a bunch for your answers,
Andrew

> Existing connections will not see the changes made, so clients that
have
> an
> existing connection should log off and logon again.
> 
> - John T.