Rusty Russell 866cca9637 libctdb: clarify logging levels ...

Now we have more messages, it seems to make sense to document their usage
and make them consistent.

In particular, LOG_CRIT for internal libctdb problems, LOG_ALERT for
API misuse.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>


(This used to be ctdb commit a6fed3f577c7ec51df38ed15ecb9db6ea2ae7c8f)

2010-06-08 16:53:17 +09:30

..

control.c

libctdb: use bool in API

2010-06-04 20:19:25 +09:30

ctdb.c

libctdb: clarify logging levels

2010-06-08 16:53:17 +09:30

io_elem.c

ctdb_req_control contains 4 padding bytes. Create an explicit pad variable here and set it to 0 when creating a control to keep valgrind happy.

2010-06-02 16:49:05 +10:00

io_elem.h

libctdb: uniform callbacks, _recv functions to pull out data.

2010-05-24 13:17:36 +09:30

libctdb_private.h

libctdb: add logging infrastructure

2010-06-04 20:27:03 +09:30

local_tdb.c

libctdb: first cut, supports getrecmaster only

2010-05-21 12:07:41 +09:30

local_tdb.h

libctdb: first cut, supports getrecmaster only

2010-05-21 12:07:41 +09:30

logging.c

libctdb: add logging infrastructure

2010-06-04 20:27:03 +09:30

messages.c

libctdb: clarify logging levels

2010-06-08 16:53:17 +09:30

messages.h

libctdb: first cut, supports getrecmaster only

2010-05-21 12:07:41 +09:30

sync.c

libctdb: use bool in API

2010-06-04 20:19:25 +09:30

TODO

libctdb: documentation

2010-06-04 20:30:08 +09:30

tst.c

Split ctdb_release_lock() into a function to release the locvk and another function to free the data structures.

2010-06-05 15:38:11 +10:00