[Samba] 2.2.9pre1 cvs - vfs module ignores SIGHUP?
Thomas Bork
tombork at web.de
Thu Sep 25 22:18:31 GMT 2003
Hi,
with 2.2.9pre1 from cvs
(ftp://pserver.samba.org/pub/unpacked/samba_2_2 - downloaded on 14. Sep
2003) the vfs modules ignores SIGHUP-ing the smbd.
Relevant Part of smb.conf:
[public]
comment = public directory on %h
browseable = yes
writeable = yes
path = /public
oplocks = no
level2 oplocks = no
blocking locks = no
public = yes
read list = tb
write list =
create mask = 0777
directory mask = 0777
vfs object = /usr/lib/samba/vscan-oav.so
vfs options = config-file = /etc/vscan-oav.conf
If normal starting or restarting samba, the scannerdaemon and
samba-vscan are working fine. But removing the vfs options from smb.conf
and kill -SIGHUP all smbds, samba-vscan is always working.
If having
[public]
comment = public directory on %h
browseable = yes
writeable = yes
path = /public
oplocks = no
level2 oplocks = no
blocking locks = no
public = yes
read list = tb
write list =
create mask = 0777
directory mask = 0777
and normal (re)starting samba, samba-vscan is not working -ok. Adding
vfs object = /usr/lib/samba/vscan-oav.so
vfs options = config-file = /etc/vscan-oav.conf
and kill -SIGHUP all smbds, samba-vscan is not working. Seemed, that vfs
modules don't recognizing SIGHUP of smbd or changes of smb.conf (every
60 seconds and for every new connection the smb.conf will scanned.
With samba version 2.2.8a there is the same problem :(
der tom
More information about the samba
mailing list