On Sun, Sep 22, 2002 at 09:55:56AM -0600, John T. Benedetto wrote about 'Re: [Samba]
updating smb.conf during Samba is working':
> On Sat, 21 Sep 2002, Andrew Bartlett wrote:
> > Hitting any smbd with a -HUP should force a reload of the config file,
> > and reopen
On Sat, 21 Sep 2002, Andrew Bartlett wrote:
> Hitting any smbd with a -HUP should force a reload of the config file,
> and reopen the logfiles etc.
>
> (ie killall -HUP smbd should work fine)
>
> Andrew Bartlett
Does that do anything bad to current connections with open files?
- john
--
To
Joel Hammer wrote:
>
> 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
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
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
>
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 se
