[or-cvs] r11324: 0-pad minutes and seconds when displaying weighted mtbf in i (in tor/trunk: . doc src/or)

[nickm@xxxxxxxx]

Author: nickm
Date: 2007-08-30 17:12:34 -0400 (Thu, 30 Aug 2007)
New Revision: 11324

Modified:
   tor/trunk/
   tor/trunk/doc/TODO
   tor/trunk/src/or/rephist.c
Log:
 r14859@catbus:  nickm | 2007-08-30 17:10:15 -0400
 0-pad minutes and seconds when displaying weighted mtbf in info logs.



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r14859] on 8246c3cf-6607-4228-993b-4d95d33730f1

Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO	2007-08-30 21:04:14 UTC (rev 11323)
+++ tor/trunk/doc/TODO	2007-08-30 21:12:34 UTC (rev 11324)
@@ -41,7 +41,7 @@
       - Tor logs the libevent version on startup, for debugging purposes.
         This is great. But it does this before configuring the logs, so
         it only goes to stdout and is then lost.
-      - Aug 30 16:57:41.196 [info] OR (unknown) [8DEF1682406EDE71479E98A4AEB1F27829911106]: 11/141 good connections; uptime 6748/319666 sec (2.11%); wmtbf 4:6:16
+      o Aug 30 [...] wmtbf 4:6:16
         The wmtbf time value is missing some zero-pads.
 
   - Proposals:

Modified: tor/trunk/src/or/rephist.c
===================================================================
--- tor/trunk/src/or/rephist.c	2007-08-30 21:04:14 UTC (rev 11323)
+++ tor/trunk/src/or/rephist.c	2007-08-30 21:12:34 UTC (rev 11324)
@@ -469,7 +469,7 @@
     }
     log(severity, LD_GENERAL,
         "OR %s [%s]: %ld/%ld good connections; uptime %ld/%ld sec (%.2f%%); "
-        "wmtbf %lu:%lu:%lu",
+        "wmtbf %lu:%02lu:%02lu",
         name1, hexdigest1,
         or_history->n_conn_ok, or_history->n_conn_fail+or_history->n_conn_ok,
         upt, upt+downt, uptime*100.0,