RFC: Change mtree nsec handling?

Peter Jeremy peterjeremy at optushome.com.au
Fri Jan 30 03:23:11 PST 2009


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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20090130/d5eb4804/attachment.pgp


More information about the freebsd-current mailing list