[tabled patch 4/4] log TDB state transition by default

Pete Zaitcev <[email protected]> Fri, 21 May 2010 20:20:08 -0600
Newsgroups org.kernel.vger.hail-devel
Message-ID <[email protected]>
This is useable because tabled is, regrettably, extremely slow to start,
and the "initialized" message that it logs is confusingly premature.
The daemon only starts accepting requests about 20 seconds later,
when the TDB transition happens.

Signed-off-by: Pete Zaitcev <[email protected]>

---
 server/server.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

commit 451f183467804f47646744599a66c7916b5dd99e
Author: Pete Zaitcev <[email protected]>
Date:   Fri May 21 19:58:27 2010 -0600

    Make DB state change visible in logs by default.

diff --git a/server/server.c b/server/server.c
index 4e8dba3..703a656 100644
--- a/server/server.c
+++ b/server/server.c
@@ -1809,8 +1809,8 @@ static void tdb_state_process(enum st_tdb new_state)
 {
 	unsigned int db_flags;
 
-	if (debugging)
-		applog(LOG_DEBUG, "TDB state > %s", state_name_tdb[new_state]);
+	applog(LOG_INFO, "TDB state %s", state_name_tdb[new_state]);
+
 	if ((new_state == ST_TDB_MASTER || new_state == ST_TDB_SLAVE) &&
 	    tabled_srv.state_tdb == ST_TDB_ACTIVE) {