Upgrading Samba on a critical system

[Andrej Borsenkow]

-----Original Message-----
From: Matt JD Aldridge <Matt.Aldridge at nexor.co.uk>
To: Multiple recipients of list <samba at samba.anu.edu.au>


>Hi everyone,
>
>What is the best way to upgrade Samba on a running system with lots of
>open files and oplocks (e.g. MS Exchange folders) without stopping and
>starting Samba?  Is it safe to simply replace the binaries,

No. Some systems will prevent you from overwriting binaries of running
program; even if it is possible, it will most probably result in crashing
running programs. The safe way is to move (rename) existing binaries and
then install new ones. Many systems have install program, which does exactly
that.

>
and, if so,
>does will this result in the new version being run?

No.

>
Can I send some sort
>of signal to the parent smbd and nmbd processes to get them to restart
>from the new binaries whilst preserving connections and file locks?
>

No. You can kill running old daemons and most clients will reconnect, but I
have no idea, what happens with oplocks - if they will be re-acquired.

Also, if old and new versions have incompatible locking scheme (or shared
memory layout) it will definitely break things.
To SAMBA team - probably, it is a good idea to indicate in release info, if
it is possible to run mixed binaries.

A. Borsenkow