[KLUG Members] Re:Samba reprocess config file questions

[members@kalamazoolinux.org]

>>>QUESTION1: Will sending a kill -sigusr1 samba.pid crash any open files
>>>onmy samba server?
>>>QUESTION 2: Will sending a kill -SIGHUP samba.pid crash any open files?
>>You can "killall -1 smbd" safely.  If you want do a smbstatus before and
>>after, you'll see all the locked/open files stay around.
>It is so hard to be productive when I have to hide for two days from a
>bunch of really mad users trying to hunt me down for crashing their samba
>sessions.
>I think the killall -1 will just increase my logging level by one.

?

-1 = -HUP

       SIGHUP        1        Hangup detected on controlling terminal
                              or death of controlling process
       SIGINT        2        Interrupt from keyboard
       SIGQUIT       3        Quit from keyboard
       SIGILL        4        Illegal Instruction
       SIGABRT       6        Abort signal from abort(3)
       SIGFPE        8        Floating point exception
       SIGKILL       9        Kill signal
       SIGSEGV      11        Invalid memory reference
       SIGPIPE      13        Broken pipe: write to pipe with no readers
       SIGALRM      14        Timer signal from alarm(2)
       SIGTERM      15        Termination signal
       SIGUSR1   30,10,16     User-defined signal 1
       SIGUSR2   31,12,17     User-defined signal 2
       SIGCHLD   20,17,18     Child stopped or terminated
       SIGCONT   19,18,25     Continue if stopped
       SIGSTOP   17,19,23     Stop process
       SIGTSTP   18,20,24     Stop typed at tty
       SIGTTIN   21,21,26     tty input for background process
       SIGTTOU   22,22,27     tty output for background process

>I also need to get smbd to re-read smb.conf without getting a whole lot of
>people irate.
>I think it is safe to do a killall -HUP smbd to reload smb.conf without
>crashing everyone.

Yes.

>While searching through the Samba docs looking for the oplocks syntax, I
>saw a sample logrotate script for samba. I checked in the cron.daily and
>logrotate.d directories and the cron logfile and found that the fileserver
>crond is running /etc/logrotate.d/samba on a nightly basis.
>This file has the killall -HUP smbd command between postrotate and
>endrotate. I think that means smbd is being forced to re-read smb.conf
>everynight. Since I often run out of here at night leaving files open, I
>think that must mean it is safe to do a kill -HUP during working hours.

Log rotate does this because (according to UNIX symattics) one can't remove or 
truncate an open file.  Samba has the log files open for logging,  thus it 
needs Samba to release them (which HUP does) so that it can rotate them.

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/