******************* This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Hi Simon, * gfal-copy with root created a directory with the default values * gfal-copy with davs it does the same but requires the -p option otherwise it fails because the directory is not there * gfal-mkdir creates directories by default with 755 but also has a -m option to override the default. I wonder if dirac creates the directories before copying the files using gfal-mkdir default? :/ cheers alessandra On 01/08/2023 17:30, Simon Fayer wrote:
Hi Alessandra,
On Tue, Aug 01, 2023 at 11:08:46AM +0100, Alessandra Forti wrote:
I'm trying to understand if it is a problem with the storage or with the client. The client is dirac either with the commands or with the python API, i.e.
j.setOutputData([FILE], outputSE=STORAGE, outputPath=PATH)
is there a way to set the permissions correctly? DIRAC is using a fairly light wrapper around the GFAL2 API, we don't think it sets any options related to the permissions. The default protocol for Manchester is currently set to root://; can you please try writing a file manually with gfal-copy using a root:// URL and see if you see the same problem at that level?
Regards, Simon
-- "Annamo a pijà er gelato?" (Sacco, Zerocalcare)