Hi,
a possible workaround is to have logrotate do a samba restart instead of a reload. This will disconnect all users, but it that is not an issue at the time logrorate is running, this might be an improvement over crashing...
appended is an smb.conf of an affected server
regards, Olivier Sessink
----------------- smb.conf ----------------------------------- [global] printing = bsd printcap name = /etc/printcap load printers = yes guest account = nobody invalid users = root security = share workgroup = fbt.wau netbios name = FBT_LINUX netbios aliases = linux1 serv.wu server string = FBT Linux server remote announce = 137.224.178.217/pk.wau 137.224.178.222 syslog only = no syslog = 0; socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096 SO_RCVBUF=4096 encrypt passwords = yes wins support = no wins server = 137.224.145.16 os level = 50 name resolve order = lmhosts host wins bcast dns proxy = no preserve case = yes short preserve case = yes unix password sync = false max log size = 1000 [homes] comment = Home Directories browseable = no read only = no create mask = 0700 directory mask = 0700 [htdocs] comment = webroot browseable = yes path = /var/www public = no writable = yes force group = wwwauthors create mask=0666 directory mode=0777 username = hylke, olivier, bertjan [intern] comment = webroot browseable = yes path = /var/www/intern public = no writable = yes force group = pk create mask=0666 directory mode=0777 username = hylke, olivier force user = hylke, olivier [smart] comment = smart project browseable = yes path = /home/smart public = no writable = yes force group = smart create mask=0666 directory mode=0775 force user = smart
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]