[SCM] Samba Shared Repository - branch master updated

Volker Lendecke Volker.Lendecke at SerNet.DE
Mon Jul 5 07:35:12 MDT 2010

On Mon, Jul 05, 2010 at 09:28:27AM -0400, simo wrote:
> It is not a policy, I was just asking if it made sense to do so.
> Allowing for seamless upgrades when possible is a good thing, and we
> often added functions to upgrade internal DBs when the DB format
> changed.
> Is this something we decided is not worthy anymore ?

Well, connections.tdb is a CLEAR_IF_FIRST database. The new
policy requires that in a cluster, version x needs to run
simultaneously with version y. This means that for the
CLEAR_IF_FIRST databases we need to maintain strict
compatibility. This also applies to all protocols with
messaging style messages, for example it also applies to

This is what I mean with ROLLING code upgrade. In a cluster,
you upgrade one node after the other while everything needs
to keep running. When everything is on the new software
version, then we can start using new structures after an
internal freeze and upgrade of data structures has taken
place while the cluster is humming along.

BTW, I am NOT talking about persistent databases like
secrets.tdb that must survive a restart of smbd, I am
talking about databases like locking.tdb that will wiped
once smbd shuts down.

Possible to do, but severely restricts our design space. But
if that is the new policy we need to do it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100705/8e3294e9/attachment.pgp>

More information about the samba-technical mailing list