On Mon, 25 May 2009, Arnaud Quette wrote: > > elapsed time (seconds and microseconds) since the first upsdebug() > > command by default without requiring any additional command line > > options. We're probably more interested in the elapsed time since > > the program started anyway, instead of wall clock time when > > debugging something. > > right, it's best for our use case. > a good thing would be to add the start time (at driver startup) or an > option to turn this into timestamps when debugging cross components > (like driver-upsd communication) to avoid recalculation.
Hmm.. won't relative timestamps make it difficult when you're debugging program interaction? eg a UPS driver & upsd. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
