Displaying 2 results from an estimated 2 matches for "7200s".
Did you mean:
7200
2020 May 14
1
system(timeout=) may timeout with 0 exit code
...cmd, timeout_s, proc.time()[[3L]]-p, warn),
file="timeout-exit-codes.out", append=TRUE)
And the content of timeout-exit-codes.out:
command '/bin/bash -c "./_launcher/solution.R > log.out 2> log.err"'
timed out(?) but still exited with 0 code, timeout 7200s, took
7220.005s, warning '/bin/bash -c "./_launcher/solution.R > log.out 2>
log.err"' timed out after 7200s'
Thank you,
Jan Gorecki
2005 Jan 19
1
PROPOSAL: --link-hash-dest, additional linking of files to their HASH values
...ardlinked (basically the ones rsync already hardlinked to the
previous backup - assumes users aren't hardlinking their own files).
Using this patch would save a pass through the inodes and be a big win
(30-50% faster? Almost the same as upgrading to 10K RPM disks, keeping the
250G+ size of 7200s) The utilities may prove useful migrating existing
backups to this hash structure, recovering lost hash directories, and
pruning the hash directory. I'd like to make these utilities use the same
hash structure and race-avoidance an rsync hashdir-patch uses.
-Drake <diedrich@usc.edu>