Displaying 3 results from an estimated 3 matches for "mindata".
Did you mean:
indata
2005 May 11
2
time zones, daylight saving etc.
...has become "16/03/2003 00:02"
i.e. it is 12 hours behind (as is everything else), but also, I do not
want to change time zones.
The 12 hour delay is not really a problem just an annoyance, but the
time zone change is a problem because later on I need to match up data
by time using
mindata<-seq(from=min(datetime),to=max(datetime),by="mins")
newdata<-matrix(0,length(mindata),1)
newdata[match(format.POSIXct(datetime,"%Y %m %d %H
%M"),format.POSIXct(mindata,"%Y %m %d %H %M"))]<-data$V3
and things go wrong here with matching repeating times/missin...
2019 May 16
0
[nbdkit PATCH 2/2] cache, cow: Round size down
...d plugin:
nbdkit --filter=blocksize nbd maxdata=32M socket=/path/to/socket
+Serve a file as if it were a block device that insists on 4k
+alignment, while still allowing access to any unaligned bytes at the
+end of the file:
+
+ nbdkit --filter=blocksize --filter=truncate file /path/to/file \
+ mindata=4k round-up=4k
+
=head1 SEE ALSO
L<nbdkit(1)>,
L<nbdkit-nbd-plugin(1)>,
L<nbdkit-vddk-plugin(1)>,
-L<nbdkit-filter(3)>.
+L<nbdkit-filter(3)>,
+L<nbdkit-truncate-filter(1)>.
=head1 AUTHORS
diff --git a/filters/cache/nbdkit-cache-filter.pod b/filters/cache/...
2019 May 16
3
[nbdkit PATCH 0/2] Avoid oddities with files unaligned to granularity
When using a filter that rounds up to alignment boundaries, the tail
bytes of the plugin are difficult to access correctly. Rather than
duplicating lots of code already in the truncate filter, it's easier
to just make the other filters default to rounding down and add doc
links on how to round up instead.
Eric Blake (2):
blocksize: Lift restriction against 0-size file
cache, cow: Round