[Announce] Samba 4.3.1 Available for Download

[Volker Lendecke]

On Mon, Oct 26, 2015 at 11:12:12PM +0100, Thomas Bork wrote:
> Am 26.10.2015 um 11:56 schrieb ich:
> 
> >No daemon, tdbbackup complains:
> >+ for tdb in '$lockdir/?*.tdb' '/etc/?*.tdb'
> >+ '[' -f /var/lock/samba/gencache_notrans.tdb ']'
> >+ rm -f /var/lock/samba/gencache_notrans.tdb.samba.bak
> >+ /usr/bin/tdbbackup -s .samba.bak /var/lock/samba/gencache_notrans.tdb
> >tdb_mutex_open_ok[/var/lock/samba/gencache_notrans.tdb]: Can use mutexes
> >only with MUTEX_LOCKING or NOLOCK
> >Failed to open /var/lock/samba/gencache_notrans.tdb
> >+ /usr/bin/tdbbackup -v /var/lock/samba/gencache_notrans.tdb
> >And no I can see, why tdbbackup complains:
> >testeis # tdbbackup -h
> >Usage: tdbbackup [options] <fname...>
> >
> >    -h            this help message
> >    -s suffix     set the backup suffix
> >    -v            verify mode (restore if corrupt)
> >    -n hashsize   set the new hash size for the backup
> >    -l            open without locking to back up mutex dbs
> >I have to use '-l' now for such tdbs.
> 
> I have to ask the other way around:
> Why is gencache_notrans.tdb the only tdb, which has to back up with
> tdbbackup with '-l'? Is it the only mutex db?

By default that's the only one, right. We have

dbwrap_tdb_mutexes:* = true

to enable the much faster mutex for all tdbs. You can
replace the "*" with for example "locking.tdb" to enable
mutexes only for individual tdb files.

What I don't get however: Why do you want to backup those
tdbs? They are created with CLEAR_IF_FIRST, meaning they are
wiped when Samba starts anyway.

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de