I believe you just send a sighup to the original smbd daemon. The pid when you compile from source with defaults is here: /usr/local/samba/var/locks/smbd.pid It may be in /var/lock or other places. Or, ps ax | grep smbd and usually, if smbd is started on reboot, the lowest pid is your original one. In linux, signal 1 is sighup, so: kill -1 pid makes smbd reread smb.conf but current connections are not altered. I do not know what happens if you sighup a daughter smbd process. YMMV. Joel
On Fri, Sep 20, 2002 at 01:09:10PM +0200, Harry Rüter wrote: > Hi, > > as far as i know, there's no other solution than > restarting the server. > > Can't believe changing smb.conf has any effect on > already running servers, maybe on new child-processes ... > > If it's critical, you have to do the changes, when there's no > user/client connected .. > > Greets Harry > > > Hi > > > > I have the following problem. > > I like to make changes in the smb.conf during the samba server is still > > > > working. > > And it should take affect this updates without restarting the server. > > Sometimes it works, sometimes after long waiting, sometimes it does not > > > > take affect. > > > > Is there some options to set, or do you know another solution ? > > > > Thank you > > > > Greetings > > > > Markus Rölle > > -- > Werden Sie mit uns zum "OnlineStar 2002"! Jetzt GMX wählen - > und tolle Preise absahnen! http://www.onlinestar.de > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba