Re: RFC: Change mtree nsec handling?

From: Peter Jeremy <peterjeremy_at_optushome.com.au>
Date: Fri, 30 Jan 2009 22:23:07 +1100
On 2009-Jan-30 01:43:35 -0800, Maxim Sobolev <sobomax_at_freebsd.org> wrote:
>Tim Kientzle wrote:
>> For example, a timestamp of 1233295862.000001
>> (1233295682 seconds and 1000 nanoseconds)
>> will be printed like this by mtree:
>>    time=1233295862.1000
>> Unsurprisingly, the mtree parsing works the same
>> way in reverse.
>
>Given the age of mtree(8) I guess there are lot of existing mtree specs 
>out there who rely on this behavior.

The existing code to read nanoseconds will handle either the old
format or a %09d format (the for() loop that Tim added is unnecessary)
so existing specs won't have a problem.  I think adding leading zeroes
is the correct way to proceed.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.

Received on Fri Jan 30 2009 - 10:23:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:41 UTC