 |
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? |
|
|
Hello, I'm facing the same issue and assume it is caused by this bug? https://github.com/systemd/systemd/pull/15318 RockyLinux 8 currently only provides systemd v239, is it possible to upgrade this to v246+ to get the update? By the way, I have tried setting UMask settings in all the different places and none have worked. The nautilus processes spawned by systemctl --user always stays at 022. /etc/pam.d/common-session /etc/pam.d/login /etc/login.defs /etc/default/login /etc/systemd/system/dbus.service.d/override.conf /etc/systemd/system/user@.service.d/override.conf /usr/lib/systemd/system/user@.service /etc/systemd/user/nautilus.service.d/umask.conf Is there another way to work around this? |
|
|
Rocky Linux 8 will not receive any systemd upgrades. If you feel that you want a newer systemd, please submit a ticket to https://git.resf.org/sig_fasttrack/meta as they will soon specialize in upgraded base packages. Rocky Linux 8.10 also marks the end of Active Support. This means Rocky Linux 8 will be in maintenance mode and will no longer receive feature updates. Rocky Linux 8.10 will release with systemd-239-82.el8_10.1. You are free to view this patch here: https://git.rockylinux.org/staging/rpms/systemd/-/commit/aae896cedc332e642364bfa49c2dc71fb8ff1fa3 As this issue cannot be resolved in current Rocky Linux versions and 8.10 will be released in the coming weeks, we'll be closing this report. Closing. |
- Anonymous
