| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
change these timestamp settings without good reason.
Remove CLEAR_IF_FIRST flag is tdb is read-only.
Jeremy.
|
| |
|
| |
|
|
|
|
| |
Jeremy.
|
|
|
|
| |
this prevents the fd seek pointer problem
|
|
|
|
|
| |
parent and child share seek pointer. Damn....
Jeremy.
|
|
|
|
| |
Jeremy.
|
|
|
|
|
| |
unlock are explicitly non-blocking. I will add a comment to this effect later.
Jeremy.
|
|
|
|
|
|
|
|
|
| |
map_ptr not neccessarily set to NULL if no mmap, secondly, iterating
through a tdb was using SETLK, instead of SETLKW - would almost never
fail with mmap as the time holding the lock was so short, but was
easily seen with read/write. One finaly bug needs tracking down w.r.t.
traversal......
Jeremy.
|
| |
|
| |
|
| |
|
|
|
|
| |
header files.
|
|
|
|
|
|
| |
heavy netbench run. :)
Rework ppc spinlocks to be faster.
|
|
|
|
| |
stuff. From Andrew Esh <AEsh@tricord.com>
|
|
|
|
| |
Volker
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ok - now we're no longer trying to reach a silly 1k loc target,
change the formatting to be *readable* - eg.
change if (x) y else z to be :
if (x)
y
else
z
and other compact sillyness. Oh look - when I did this I found
some areas where we *WEREN'T CHECKING SYSTEM CALL ERROR RETURNS !!!!*
CompSci 101 guys....... :-).
Jeremy.
|
|
|
|
| |
Jeremy.
|
|
|
|
| |
Jeremy.
|
|
|
|
| |
Jeremy.
|
| |
|
|
|
|
| |
Jeremy.
|
|
|
|
|
| |
This got regressed somehow.....
Jeremy.
|
|
|
|
| |
Jeremy.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
was the initial cause of the connections database becoming corrupt.
Note that this bug only happens when doing deletions within a
traversal, which is why it has only showed up now
- added delete within traversal testing to tdbtorture
- added a lot more logging to tdb
|
|
|
|
|
|
| |
of messages from the tdb code into the Samba DEBUG() system
just call tdb_open_log() instead of tdb_open() to enable this on
any tdb
|
| |
|
|
|
|
|
|
|
| |
can't be merged don't fail the operation, instead just add
it to the free list anyway
added logging to tdb
|
|
|
|
| |
Jeremy.
|
|
|
|
| |
ENOSPC could be very bad
|
|
|
|
|
|
| |
This needs testing !
Tidied up tabs in tdb.c.
Jeremy.
|
| |
|
| |
|
|
|
|
| |
Jeremy.
|
| |
|
| |
|
|
|
|
| |
Jeremy.
|
|
|
|
| |
Jeremy.
|
| |
|
|
|
|
| |
Jeremy.
|
| |
|
|
|
|
|
| |
clients to join a Samba domain - odd or even domain name length. Needs more testing.
Jeremy.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
source/include/proto.h
- make proto
source/printing/nt_printing.c
source/rpc_server/srv_spoolss_nt.c
- Fix for the overwriting of printerdata entries when WinNT and
Win2k are modifying printer parameters on PCL printers. Turns out
that Win2k creates a printer with a NULL devmode entry and then
expects to set it on *OPEN* (yes this is insane). So we cannot
return a "default" devmode for a printer - and we must allow an
open to set it.
source/tdb/tdb.c
- Show freelist in an easier format. Show total free.
- When storing a new record, allocate memory for the key + data
before the tdb_allocate() as if the malloc fails a (sparse) hole
is left in the tdb.
source/tdb/tdbtool.c
- Show freelist in an easier format. Show total free.
source/tdb/Makefile
- cleaned up Makefile dependancies
source/smbd/lanman.c
- Fix for Win9x corrupting it's own parameter string.
source/printing/printfsp.c
source/printing/printing.c
source/rpc_server/srv_spoolss_nt.c
source/smbd/close.c
- Added normal close parameter into print_fsp_end() which treats an
abnormal close as error condition and deletes the spool file.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
struct tdb_traverse_lock tl = { tdb->travlocks.next, 0, 0 };
The IRIX compiler complained that the first initialization value was not a
constant and errored out. Here's what it looks like now:
struct tdb_traverse_lock tl = { NULL, 0, 0 };
int ret, count = 0;
/* This was in the initializaton, above, but the IRIX compiler
* did not like it. crh
*/
tl.next = tdb->travlocks.next;
That worked.
Chris -)-----
|
|
|
|
|
|
|
|
|
|
| |
When chaining together long lines of bloody "if" statements, which should
logically be separated, and one of them allocates memory, remember to
*free* it *WHETHER OR NOT THE IF STATEMENTS SUCCEEDED* !!!!
Yes I do consider this a bug in the coding style of Tridge, Rusty, Tim et al. :-).
I'm just pissed 'cos this took 4 hours to track down even with an insure error report
stating me in the face and also Ben Woodward looking over the code with me :-).
Jeremy.
|