 |
 |
Actually, we purposefully do not use the umask as it's very deceiving since it's associated with a user and a) the file creator is actually the daemon noot the user, and b) Certain plugins change the daemon's userid when creating a file. For simplicity and consistency we do not use the umask. However, we are considering allowing you to specify the mode on the xrdcp command line to provide more flexibility. The other possibility is to modify the client-side default or 0644 using the client-side umask. But even then, I think that would be somewhat confusing and may change past behaviour which we try to avoid. Andy On Wed, 4 May 2022, raffaele wrote: > One more point: wouldn't it be even better to have the file opened with the permissions decided by the local file system, in general by umask, as it happens when touching a new file? I mean instead of hard coding 644, although in the vast majority of cases 0644 is indeed what we want (and the default umask is 022). > > -- > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1642#issuecomment-1117556992 > You are receiving this because you are subscribed to this thread. > > Message ID: ***@***.***> -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1642#issuecomment-1117739162 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