mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
b8eb5925cf
If a transaction could be started, do safe transaction store when updating the record inside the daemon. If the transaction could not be started (maybe another samba process has a lock on the database?) then just do a normal store instead (instead of blocking the ctdb daemon). The client can "signal" ctdb that updates to this database should, if possible, be done using safe transactions by specifying the TDB_NOSYNC flag when attaching to the database. The TDB flags are passed to ctdb in the "srvid" field of the control header when attaching using the CTDB_CONTROL_DB_ATTACH_PERSISTENT. Currently, samba3.2 does not yet tell ctdbd to handle any persistent databases using safe transactions. If samba3.2 wants a particular persistent database to be handled using safe transactions inside the ctdbd daemon, it should pass TDB_NOSYNC as the flags to the call to attach to a persistent database in ctdbd_db_attach() it currently specifies 0 as the srvid (This used to be ctdb commit 8d6ecf47318188448d934ab76e40da7e4cece67d) |
||
|---|---|---|
| .. | ||
| client | ||
| common | ||
| config | ||
| doc | ||
| ib | ||
| include | ||
| lib | ||
| packaging/RPM | ||
| server | ||
| tcp | ||
| tests | ||
| tools | ||
| utils | ||
| web | ||
| .bzrignore | ||
| .gitignore | ||
| aclocal.m4 | ||
| autogen.sh | ||
| config.guess | ||
| config.mk | ||
| config.sub | ||
| configure.ac | ||
| configure.rpm | ||
| install-sh | ||
| Makefile.in | ||