Paolo Montrasio <address@hidden> writes:
> Failure 1)
> When a new file is created the nanosecond component of the timestamp
> cannot be set by cp. This is a quote from cp's code:
>
> Failure 2)
> The filesystem might not have a nanosecond time resolution, so we
> have to properly identify the supported resolution and the round off
> method (down or up?)
>
> As there are two different failures there should be two different solutions.
I don't see why. Both failures have the same symptoms: the time stamp
is truncated. Both failures occur at exactly the same point: the same
system call. A single solution could therefore handle both failures.