 |
Thank you for the report. This (unfortunately) sounds like normal behavior of systemd --user. In theory pam_umask can be used to set this, but it may not get inherited down the process tree. I would recommend trying this, replacing <<UID>> and <<UMASK>> as needed. % mkdir -p /etc/systemd/system/user@<<UID>>.service.d % cat > /etc/systemd/system/user@<<UID>>.service.d/umask.conf<<EOF [Service] UMask=<<UMASK>> EOF % systemctl daemon-reload After that, log out and back in. Or restart the system if all else fails. |
 |
Hi Louis, Thanks for the reply, have tried that and several other configurations but none seem to work. as you mention this is normal behaviour for Rocky 8.8, it does not seem to be present in other distro ie centos 7 which seems to inherit and keep the umask. It is important that umask is retained within a profile for all services/processes for consistency. We have tested pam_umask which also does not work. This definately seems like a bug as the umask should be inherited from the global user setting. Could you please elaborate on normal behavious as i have not seen this previously. We should be able to change this but it seems regardless of where we apply the umask setting, child processes do not inherit the umask. Do you know if the same behaviour is experienced in previous releases of Rocky Linux? |
- Anonymous
