Your message dated Fri, 6 Apr 2018 23:30:33 +0200
with message-id 
<CAFX5sbznjJova=XsGu_Xu2zw1Dfx=sUd1iwngnuxmBU=5mz...@mail.gmail.com>
and subject line Not reproducible
has caused the Debian Bug report #686589,
regarding samba: init script reload action does not signal all processes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
686589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:3.5.6~dfsg-3squeeze8
Severity: normal

Hello samba-Maintainers,

there's a problem with the 'reload' action in the samba init script, it
only signals HUP the single PID given in /var/run/samba/smbd.pid. On
(nearly?) all systems I looked at using samba, there are two smbd
processes, and the log file opened by the second process stay open:

| $ sudo lsof -n |grep deleted
| smbd      30166    root    2w      REG      254,1     5910      65672 
/var/log/samba/log.smbd.1 (deleted)
| smbd      30166    root    8w      REG      254,1     5910      65672 
/var/log/samba/log.smbd.1 (deleted)
| $ sudo service samba reload
| Reloading /etc/samba/smb.conf: smbd only.
| $ sudo lsof -n |grep deleted
| smbd      30166    root    2w      REG      254,1     5910      65672 
/var/log/samba/log.smbd.1 (deleted)
| smbd      30166    root    8w      REG      254,1     5910      65672 
/var/log/samba/log.smbd.1 (deleted)
| $ sudo service samba restart
| Stopping Samba daemons: nmbd smbd.
| Starting Samba daemons: nmbd smbd.
| $ sudo lsof -n |grep deleted
| $ 

A 'restart' instead of a reload kills all samba daemons and starts them again,
but on the one hand that is rather brutal, and on the other, logrotate doesn't
use "samba restart" but "samba reload", so the log.smbd file doesn't get
reopened.

As this loses (log) data, I've kept the priority at normal instead of minor.

| youam@brann:~$ pidof smbd
| 22782 22768
| youam@brann:~$ cat /var/run/samba/smbd.pid 
| 22768

I've tried on another system that actually sending a SIGHUP to all smbd
processes does reopen the log files, as expected.

Uli

-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
Version: 2:3.6.6-6+deb7u10

Marking as done, as per last comment.

Regards

-- 
Mathieu Parent

--- End Message ---

Reply via email to