ack, thanks. Guido
On Fri, Jan 18, 2013 at 11:22 AM, Iustin Pop <ius...@google.com> wrote: > On Fri, Jan 18, 2013 at 10:59:40AM +0100, Guido Trotter wrote: >> On Thu, Jan 17, 2013 at 3:06 PM, Iustin Pop <ius...@google.com> wrote: >> > Currently the Haskell logging goes with the default time formatting, >> > which lacks sub-second resolution. This is not good, as it's too >> > coarse. >> > >> > The patch adds picoseconds to the log; they will contain usually too >> > many zeroes, but the other option is to use a log format that (for >> > precisely zero fractional part) omits the separator, so it's not >> > consistent from line to line, and which also uses a dot as a >> > separator, different from the Python code. >> > >> > Signed-off-by: Iustin Pop <ius...@google.com> >> >> Who hasn't ever wanted picoseconds. >> Ok, ok, LGTM if there's no way to just format microseconds or so! :) > > Nope, in the time formats it's either picoseconds (the %q here) or the > variable-length format (%Q). There's another way to add custom variables > to the log formatter but use I/O callbacks but I think that's too heavy… > > thanks, > iustin -- Guido Trotter Ganeti engineering Google Germany
