[KLUG Members] Re:Samba reprocess config file questions

[Bob Kanaley]

> Date: Wed,  6 Mar 2002 14:26:32 -0500
> From: adam@morrison-ind.com
> To: members@kalamazoolinux.org
> Subject: Re: [KLUG Members] Samba reprocess config file questions
> Reply-To: members@kalamazoolinux.org
>
> >QUESTION1: Will sending a kill -sigusr1 samba.pid crash any open files on
> >my 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.
>

Many thanks for the info.

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.

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.

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.

In case I am wrong about this, I will be updating my resume this evening
should anyone on the list know of any job openings.