summaryrefslogtreecommitdiff
path: root/source3
AgeCommit message (Collapse)AuthorFilesLines
2008-08-14Put prototypes of modules/vfs_hpuxacl.c to new modules/vfs_hpuxacl.h.Michael Adam2-0/+62
Thereby (hopefully) fixing the potential build problems with HPUX acls. Michael (This used to be commit 4f2a1de990dc9063a1db877c06a5c1d68924edcf)
2008-08-14Put prototypes of modules/vfs_solarisacl.c to new modules/vfs_solarisacl.h.Michael Adam2-0/+49
Thereby (hopefully) fixing the potential build problems with solaris acls. Michael (This used to be commit 8413c05afcde65006fa7c8743f30b53cc33c1729)
2008-08-14Put prototypes of modules/vfs_tru64acl.c to new modules/vfs_tru64acl.h.Michael Adam2-0/+49
Thereby (hopefully) fixing the build with tru64 acls. Michael (This used to be commit 1ab64b69850489a2648a2543da6d0e1157df68bc)
2008-08-14Put prototypes of modules/vfs_posixacl.c into new modules/vfs_posixacl.h.Michael Adam3-18/+50
Michael (This used to be commit 876f6793434174051084b17f3b02bd1bbb24ec44)
2008-08-14Fix coverity CID: 594. Resource leak on error path.Jeremy Allison1-2/+4
Jeremy. (This used to be commit 1f38b9963c4ec0d73da496a72ba4ee74d8d581c9)
2008-08-14Fix for bug #5688 from SATOH Fumiyasu <fumiyas@osstech.co.jp>. LPQ process ↵Jeremy Allison1-1/+2
is orphaned if socket address parameter is invalid. If the "socket address" parameter is a null string that is an invalid value for Samba 3.2 but valid for Samba 3.0. Jeremy. (This used to be commit c65726d418601cdc86202c0371615e4f7f3d843c)
2008-08-14Fix for bug #5617, reported and patched by Bartosz Antosik antosik@gmail.com.Jeremy Allison1-0/+2
xp/2003 explorer freezes browsing shares on samba ipv6 hosts. Caused by missing reply packet to SMB printclose packet. Jeremy (This used to be commit ecf2b906f476e4a764d0e53eed84b9b75a2062c0)
2008-08-14Prevent NT_STATUS 0xF1000000 errors from appearing whenJim McDonough1-0/+6
dos errors are used and there is no error. It should be mapped directly to NT_STATUS_OK. smbclient to older servers didn't work. (This used to be commit 78f009b7ef1f1d63b21df9ba6da7fcca01c12109)
2008-08-14Revert "Add winbind:online check timeout parameter"Volker Lendecke1-16/+0
This reverts commit 9920473cc165e75ee9aa5cbb9e568eb5fb67e9e6. (This used to be commit 34a32db9060e7b60455774f923f61b7367ee3fcf)
2008-08-13Revert "If it is a forced DOS error, nt_errstr should say so"Volker Lendecke1-5/+0
This reverts commit ef5489ac805237274d6088aaa7ae870cc0deb52f. (This used to be commit e987e9956f02557c7ec87a369b92f87083fda620)
2008-08-13If it is a forced DOS error, nt_errstr should say soVolker Lendecke1-0/+5
(This used to be commit ef5489ac805237274d6088aaa7ae870cc0deb52f)
2008-08-13VERSION: Raise version number.Karolin Seeger1-3/+3
Karolin (This used to be commit 1ed4b2151e60050455e0b3564afe01b0c030b71e)
2008-08-13netapi: add c++ guard.Günther Deschner1-1/+8
Guenther (This used to be commit c9e38fef647520e4038f04bd163678bf4b30853d)
2008-08-13smbd: prevent smbd from panicing with "clustering = no" but ↵Michael Adam1-1/+3
--with-cluster-support Michael (This used to be commit a687949d19ba9690f96e7869aa22e4d87840640e)
2008-08-13added a explanatory comment on tcon checkAndrew Tridgell1-0/+4
(This used to be commit f2ab2cebb9b81453dc0b6370288b85909182ae49)
2008-08-13smbd/conn: fix prototype change of conn_close_all() in proto.h.Michael Adam1-1/+1
(Cleaning "ensure we exit with non-zero status on EOF on socket" after rebasing to v3-3-test which has no "make proto" anymore.) Michael (This used to be commit a958c6bf1e0394e98df286974d78d3b07498e0b4)
2008-08-13ensure we exit with non-zero status on EOF on socket, so the parentAndrew Tridgell2-5/+13
can trigger a brlock db cleanup (This used to be commit bbd49f9e1c4b50c4a596fb991f3306e1e90c0177)
2008-08-13fixed child exit handling and IP release handlingAndrew Tridgell2-1/+5
(This used to be commit 6fe27d296c389473c24e8c627a61bd56b364ad9f)
2008-08-13log unclean shutdownsAndrew Tridgell1-0/+1
(This used to be commit 30b83245a22ebd5e4fa4739dd2aa1805373a7eb2)
2008-08-13register the ctdbd reconfigure messageAndrew Tridgell2-0/+12
(This used to be commit 9d3217bb28765e107c230fb90b578dcc6f5d4375)
2008-08-13allow nested ctdb transactions in the same manner that they areAndrew Tridgell1-2/+21
allowed for tdb. This is needed for the registry db backend. (This used to be commit 4b04ec29c76df837a7909725bbbf4c79d5abdb4d)
2008-08-13drop retries to 5Andrew Tridgell1-1/+1
(This used to be commit a2f70fc175b748ef160a998d0563c28381ea3466)
2008-08-13use CTDB_CONTROL_TRANS2_COMMIT_RETRY to prevent the counter gettingAndrew Tridgell1-2/+3
out of sync (This used to be commit 571ec7893c8b40959c005d510c039e3f231ffc67)
2008-08-13fixed lots of places that paniced on a failed transaction_commit,Andrew Tridgell5-16/+21
thinking it was a failure of a transaction cancel (This used to be commit 22dbe158ed62ae47bbcb41bba3db345294f75437)
2008-08-13don't leave a dangling transaction on retry errorAndrew Tridgell1-2/+4
(This used to be commit ddf3022595fe8ca378c5f52107f42e296f852685)
2008-08-13cope with the control failing completely without returning a statusAndrew Tridgell1-12/+18
(This used to be commit fe6a03e7b11cd859fddae5ba924ea5e071b8ccea)
2008-08-13handle two special casesAndrew Tridgell1-16/+42
1) when all nodes write the same value to the record, or when writing a value that is already there, we can skip the write and save ourselves a network transactions 2) when all remote nodes fail an update, and we then fail a replay, we don't need to trigger a recovery. This solves a corner case where we could get into a recovery loop (This used to be commit 2481bfce4307274806584b0d8e295cc7f638e184)
2008-08-13put a limit on the number of retries. I found a case where a recoveryAndrew Tridgell1-0/+12
could lead to it blocking forever (This used to be commit a633390d3a7cb04a7c4e14cba9c533621793287e)
2008-08-13we need to commit, not cancel, on record destructionAndrew Tridgell1-1/+4
(This used to be commit ba64a757f86fb60994e12e81416083ac0fa11c21)
2008-08-13removed more unused codeAndrew Tridgell1-72/+0
(This used to be commit 30a697c82db53f9d801e220a7c6277f873ebce67)
2008-08-13all persistent databases now do all stores via automatic transactionsAndrew Tridgell1-150/+46
(This used to be commit 76fbe56e827193d939676da23a580aa0f9394dd1)
2008-08-13use transactions in idmap_tdb2Andrew Tridgell1-18/+42
(This used to be commit 32b8db27652a66a2ade547a6d27f34d0816f7296)
2008-08-13fixed fetch of empty recordsAndrew Tridgell1-6/+11
(This used to be commit 037516f1362c8d64da1d47a0cdaf83198d3eaeaf)
2008-08-13samba3 can't handle NOREPLY yetAndrew Tridgell1-0/+3
(This used to be commit 21729256a550509c3c038efa5acdd6ac39027dce)
2008-08-13cleanup debugging and fix handling of empty transactionAndrew Tridgell1-13/+11
(This used to be commit 2e85cbe88b3d1674b915f62e02be7d005fddaa39)
2008-08-13first cut at adding full transactions for ctdb to samba3Andrew Tridgell18-1390/+648
(This used to be commit f91a3e0f7b7737c1d0667cd961ea950e2b93e592)
2008-08-13got rid of the redundent cache databaseAndrew Tridgell1-134/+28
(This used to be commit 126f4ac8e85458ee4693b89a184b99420f1b6bee)
2008-08-13idmap tdb2: fix inconsistent mappings by checking for race and retrying to ↵Michael Adam2-57/+22
fetch mapping. Michael (This used to be commit cb4c74c9c206e5a445ca636fa6562ce721ea5839)
2008-08-13dbwrap ctdb: fix a DEBUG message.Michael Adam1-1/+1
Michael (This used to be commit d776d8df262e1753fb428450140df94e63035af5)
2008-08-13idmap tdb2: fix broken logic in tdb2_delete_bystring().Michael Adam1-5/+8
1. use the return value that idmap_tdb2_open_perm_db() gives us 2. don't delete frep the local db if deleting from the perm db failed. 3. fix wrong interpretation of return value of the local delete Michael (This used to be commit 147573d7f6faab0ad90258b6a28c4b9575ccb6ea)
2008-08-13idmap tdb2: fix broken logic in tdb2_store_bystring().Michael Adam1-5/+8
1. use the return value that idmap_tdb2_open_perm_db() gives us 2. don't write to the local db if writing to the perm db failed. 3. fix wrong interpretation of return value of the local store Michael (This used to be commit be8c6b4f2f40014313899b5cbc1da9d390d94fee)
2008-08-13dbwrap ctdb: don't retry when tdb_store failed in db_ctdb_persistent_store().Michael Adam1-0/+1
Only retry when ctdbd_persisten_update() failed. Michael (This used to be commit ff413a4614c8b272a34b2a9e56a329a8e8749a34)
2008-08-13dbwrap ctdb: add a partial mapping from tdb_error to NTSTATUS and use it for ↵Michael Adam1-3/+26
store. Michael (This used to be commit eaf76c751f9bde2843174b400c109304831df83e)
2008-08-13dbwrap ctdb: add db_ctdb_delete_persistent() and use it for persistent DBsMichael Adam1-1/+17
as delete_rec operation from fetch_locked() Michael (This used to be commit f4aab595a0219305fbedf8890e787b690660a55a)
2008-08-13dbwrap ctdb: call db_ctdb_store() in db_ctdb_delete().Michael Adam1-7/+2
to reduce code duplication. Michael (This used to be commit 09a197e756459877cab7b4d09f534c6a41cfdd71)
2008-08-13dbwrap ctdb: add a retry loop to the persistent store operation.Michael Adam1-51/+120
This is because ctdbd can fail in performing the persistent_store due to race conditions, and this does not mean it can't succeed the next time. To not loop infinitely, this makes use of a new parametric option: "dbwrap ctdb:max store retries" (integer) which defaults to 5 and sets the upper limit for the number or repeats of the fetch/store cycle. Michael (This used to be commit 2bcc9e6ecef876030e552a607d92597f60203db2)
2008-08-13dbwrap ctdb: release the lock before calling ctdbd_persistent_store()Michael Adam1-0/+26
in the persistent db_ctdb_store operation. This is to prevent deadlocks in db_ctdb_persistent_store(). There is a tradeoff: Usually, the record is still locked after db->store operation. This lock is usually released via the talloc destructor with the TALLOC_FREE to the record. So we have two choices: - Either re-lock the record after the call to persistent_store or cancel_persistent update and this way not changing any assumptions callers may have about the state, but possibly introducing new race conditions. - Or don't lock the record again but just remove the talloc_destructor. This is less racy but assumes that the lock is always released via TALLOC_FREE of the record. I choose the first variant for now since it seems less racy. We can't guarantee that we succeed in getting the lock anyways. The only real danger here is that a caller performs multiple store operations after a fetch_locked() which is currently not the case. Michael (This used to be commit d004c9a7281d2577c3ba2012c8f790cc198ea700)
2008-08-13dbwrap ctdb: remove erroneously duplicated comment.Michael Adam1-1/+0
Michael (This used to be commit c939c55e5182258092faceefa58a7f328f18619e)
2008-08-13Use transaction start/cancel for persistent writes to avoid leaving the ↵Ronnie Sahlberg3-6/+48
database in an inconsistent state if we crash during the operation Signed-off-by: Ronnie Sahlberg <ronniesahlberg@gmail.com> (This used to be commit 09329f1f9114af44fc4e5e4f29a7315912313125)
2008-08-13Add a gpfs_prefetch moduleVolker Lendecke3-1/+315
This can not go upstream yet because it uses the non-GPL libgpfs. So it will not be compiled by default and will not be included in the SOFS RPMs. But upon Sven's request, we include it in the git tree and the source RPMs, so that it can be built for in-house tests. (This used to be commit fc9b30bed2d774dca6660b497cb50f982b23b885)
generated by cgit (git 2.34.1) at 2024-12-30 00:36:47 +0000