<br><br><div class="gmail_quote">2009/5/25 Daniel O'Connor <span dir="ltr"><<a href="mailto:doconnor@gsoft.com.au">doconnor@gsoft.com.au</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, 25 May 2009, Arnaud Quette wrote:<br>
> > elapsed time (seconds and microseconds) since the first upsdebug()<br>
> > command by default without requiring any additional command line<br>
> > options. We're probably more interested in the elapsed time since<br>
> > the program started anyway, instead of wall clock time when<br>
> > debugging something.<br>
><br>
> right, it's best for our use case.<br>
> a good thing would be to add the start time (at driver startup) or an<br>
> option to turn this into timestamps when debugging cross components<br>
> (like driver-upsd communication) to avoid recalculation.<br>
<br>
</div>Hmm.. won't relative timestamps make it difficult when you're debugging<br>
program interaction? eg a UPS driver & upsd.<br>
</blockquote></div><br>yup, that was the core of my last reply... (an option to override the elapsed time and switch to a timestamp system).<br><br>Arjen's version (elapsed time) is very nice for working on 1 component, while the timestamp would help more in cross components (program interaction). possibly using the new "-T" to switch to the timestamp mode...<br>
<br>cheers,<br clear="all">Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>