[wdp, 10/29/08]
The refresh method of the smb/server service waits for SIGHUP, then signals a condition variable to wake up the refresh thread. The refresh thread then reloads the configuration and applies any changes. However, when thread in main() is not blocking in sigsuspend(), any additional SIGHUPs will be missed, as the signal handler does not track how many SIGHUPs the process has seen. If the process received SIGHUP while it is
refreshing (but before it has reentered sigsuspend()), it may miss that signal and not reload the most recent configuration data.
Sun Microsystems Inc. SunOS 5.11 cifs-nightly-build-11-17-2008 Nov. 18, 2008
SunOS Internal Development: jb150015 2008-11-18 [nightly-cifs-x86]
bfu'ed from /net/cifsgate.central/export/cifsnv/gate/archives/i386/nightly/ on 2008-11-18
See CR6762558