 |
 |
I think we're getting quite distracted by the fact that I'm streaming the file. The crux of it is, if I am making a new file that I am writing to xrootd with the File() object, using the `File.open` command with OpenFlags.NEW, and I know what the checksum of the file should be, it seems reasonable to me to be able to specify what that checksum should be so that xrootd can do the same verification it would during a xrdcp command. From the man page: "[the -C flag] obtains the checksum of type (i.e. adler32, crc32, or md5) from the source, computes the checksum at the destination, and verifies that they are the same. If a value is specified, it is used as the source checksum" There is no option to do this at the moment. As you mention, for the case where you're not creating a new file it would not make sense, but for my case I believe it does - there's no functional difference between (a) copying a file from a source to a location and (b) writing known data to a new file at a location. The fact I am streaming the data from source as part of (b) is merely because it is too big to guarantee fitting into memory, it is irrelevant to the rest of the argument. If my use case is not general enough that's fine, we can just close the issue. And you're definitely right, reading the source has indeed proved to be more useful in many cases than reading the documentation :) -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/2071#issuecomment-1685921617 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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