Age | Commit message (Collapse) | Author | Files | Lines |
|
Guenther
(This used to be commit 579fb55b7556dc90b42f77d5fc9e9c31f34974e5)
|
|
r23977.
Michael
(This used to be commit a3506f291abfb8a9516b79c10c79841a7391651e)
|
|
(This used to be commit 4a5fa715a6af281282092644817599f79806981d)
|
|
(This used to be commit 26d1430283bd4ae8b8a84f3253e33417d509c1a4)
|
|
(This used to be commit eabe796e464e5fe10d0f4cca1362985c529f5a5b)
|
|
Michael
(This used to be commit de0ef9134650e3e7cc5b5cfec9e8dd8510bd6677)
|
|
error condition to write. This is in tdb_new_database.
Fix one call to tdb_new_database in tdb_open_ex to not
overwrite the newly propagated errno (typically ENOSPC).
Michael
(This used to be commit 24fed55d72a4922bfd3ddba61449fbae01365feb)
|
|
* prevent infinite loops due to 0 bytes written:
try once more. if we still get 0 as return,
set errno to ENOSPC and return -1 (error)
* replace int by correct types (ssize_t and size_t).
* print a warning log message in case "written < requested to write"
usually this means, that the next call to pwrite will fail
with return value -1 and set errno accordingly.
Note that the former error condition "written != requested to write"
is not a correct error condition of write/pwrite. If this is due
to an error, a subsequent call to (p)write will reveal the cause
(typically "no space left on device" - ENOSPC).
Michael
(This used to be commit 5b8d53dfe1872621bf28c8351d87bfc53ef6e66b)
|
|
The proper error condition is (ret == -1) instead of
(ret != number_of_byte_told_to_write).
Michael
(This used to be commit e3af95f0983e9f92c10a80ee4f15a0cd718a4728)
|
|
(This used to be commit c676a971142d7176fd5dbf21405fca14515a0a76)
|
|
(This used to be commit 1b78cace504f60c0f525765fbf59d9cc6506cd4d)
|
|
Jeremy.
(This used to be commit d7b39e4534d85c84e8b24668ab7d7a93d5647c23)
|
|
say "locks chain and returned record", not
"and returns record"
Jeremy.
(This used to be commit bf951e3d7f0310cc624abab11a7fb04c50770425)
|
|
travlocks.lock_rw for lock read/write types, it
was sometimes using it (tdb_next_lock) and
sometimes explicitly using F_WRLCK instead.
Change this to consistently use travlocks.lock_rw
only.
I'm pretty sure about this fix (else I woudn't
be checking this in :-) but tridge and Volker
please review.
Jeremy.
(This used to be commit d0b64567630ec02eb437aa713847bb23a8be8a60)
|
|
optimization.
(This used to be commit 945f73fa39ba6f2b637379ac20d52b4d0306d77f)
|
|
metze
(This used to be commit 56e31d60c672689e934fbed2794c7c54cf874b11)
|
|
this function should be static
metze
(This used to be commit f722fd32da56aabca2fffe243e89177bc23e2be7)
|
|
and make the functions static.
also use libreplace headers in tdbbackup.c
metze
(This used to be commit 1ca12b1c9e7e8267fa13a40ebeb2bdcd199237de)
|
|
metze
(This used to be commit c7def92a9c2e17c90061ef17bc14e36250574e85)
|