X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=website%2Fbugs%2Fuseful_information.mdwn;h=025d678333813f9acbf5cbe5bb15ecbab8e5586c;hb=5df09d935f33477cdd9763c0e9c1ba7c8073aea0;hp=62094bb2dbcbc5a641a16bedc5adb98e1eab3ebe;hpb=2d4d7735c039f2e8623771c5b7ead05aa85831ec;p=monkeysphere.git

diff --git a/website/bugs/useful_information.mdwn b/website/bugs/useful_information.mdwn
index 62094bb..025d678 100644
--- a/website/bugs/useful_information.mdwn
+++ b/website/bugs/useful_information.mdwn
@@ -1,5 +1,5 @@
 I would like to know, at INFO (default) log level, when the 
-monkeyspehere makes a "real" modification to my known_hosts file; that 
+monkeyspehere makes a "real" modification to my known\_hosts file; that 
 is, when it adds or deletes a key.
 
 Apparently this is hard because monkeysphere is currently configured to 
@@ -22,3 +22,29 @@ known_hosts file, i get the following to stderr:
 
 This doesn't fully close this bug, because we aren't notifying on key
 deletion, afaict.
+
+------
+
+So current log level DEBUG will output a message if the known host
+file has been modified.  If the issue is that you want to know at the
+default log level everytime the known\_hots file is modified, then we
+should just move this message to INFO instead of debug, and then maybe
+remove the message that I added above.  I was under the impression
+that the issue was more about notification that a *new* key was added
+to the known\_hosts file, and therefore the new INFO message above
+fixed that problem.  Should we do this instead?
+
+In general, more verbose log levels *do* tell the user what the
+monkeysphere is doing.  Moving to DEBUG log level will tell you pretty
+much everything that happens.  I do *not* think that this should be
+the default log level, though.
+
+------
+
+I wouldn't want to see an extremely verbose default log level.  But i
+do think that saying something like "key blah blah blah was stripped
+from your known\_hosts file because it was expired" (for example)
+would be useful.  I think this case would occur infrequently enough
+that it is worth reporting in the UI at the regular log level.
+
+  --dkg