By default Samba will read the configuration file every 60 seconds so no HUP is needed. I have however done this without affecting currently connected users. The caveat is that if configuration changes are made to shares that users are already connected to, those changes will not be seen. If changes to the underlying UNIX file system is changed(protectecions primarily) then another set of problems may occur.
HTH, spike David Landgren wrote: > You can send all the processes a HUP and they will reload the config. > Ordinarily this should not affect them (unless the config change is, > for instance, the suppression of a share they happen to be using). > > smbstatus -p | tail +5 | awk '{print $1}' | xargs kill -HUP > > The above should do the trick. Yes, there are probably killall or > killproc commands that do this, but they have the same name from one > OS or distro to another. > > David > > On Mon, 31 Jan 2005 11:46:21 +0100, fluppe <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > i am planning to use samba in my company, first on a test system and > > later on operational. > > I have a question about reloading the configuration file. > > > > When i do some changes in the configuration file about mappings etc for > > new users, new folders on request etc and i have to reload the > > configuration, is that a problem for the connected users ? > > > > Will they lose their connection while they are writing or saving or > > whatever ? > > > > cheers, > > Phil. > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: https://lists.samba.org/mailman/listinfo/samba > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba