Use sane file permissions on gzipped files from publishing jobs
When extracting the MarcXML-files from a publishing job, the extracted files by default have unix file permissions set to 060 (u=,g=rw,o=), i.e. only readable and writable by the group, not by the user. This is weird and makes little sense.
Even worse, it also means that on systems with default umask of 022, which is very common, the effective permissions will be 040 (u=,g=r,o=) which means that the files can be neither changed nor deleted – even by the user who extracted them – without messing with permissions.
I can see no reason whatsoever for preferring the current default set of permission over 660, which would give the user the same permissions as the group, and also not break usage when the umask is 022.
I've had this as a support case, where all I got was that it is "by design", but no answer to why. Bad design is not a reason.
As a duplicate of this idea has received more traction I will move my votes there and suggest that you do so too:
As the other idea