 |
 |
No, a user need not write anything. The site has to decide whether or not check sums are to be supported for file systems that aren't able to record the check sum value because it potentially implies a lot more of I/O and may be more resource intensive than a site wishes. If a site is OK with check sum re- computation, the above config line would simply be: xrootd.chksum max 2 md5 adler32 crc32 prog2-compute-checksum The client has no notion that this is being done but the site specifically allows it by supplying the appropriate program (which, in single checksum cases, may be a two line shell script). Now, if you are saying the site should be able to compute check sums without storing the result for future queries and avoid writing a small script, then certainly post an enhancement request (i.e. some option on the directive that allows that to happen). The point here is that potentially resource intensive operations should be explicitly enabled. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/769#issuecomment-406902331 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1