On 3/21/26 18:43, Borden wrote:
Question: systemd has permission gotchas, specifically in denying read/write access to the home directory. I also read that uwsgi is very fussy about folder permissions.Under init.d, I got away with storing my radicale collection in my home folder. Will systemd break this? How difficult will the workaround be to getting this working?
1) One way (untested) could be to disable dynamic user configuration on your machine after ensuring the 'radicale' system user and group exist.
# addgroup --system radicale# adduser --system --ingroup radicale --no-create-home --home /var/lib/radicale radicale
# mkdir -p /etc/systemd/system/[email protected]# echo -n "[Service]\nDynamicUser=no\n" > /etc/systemd/system/[email protected]/mychanges.conf
# systemctl daemon-reload # systemd stop [email protected]After this you could be able to symlink /var/lib/radicale to your home directory and the change ownership to radicale:radicale.
2) Another way (untested) to achieve this is perhaps to try link /var/lib/private/radicale to a path in your home directory. Then chown nobody:nobody on this directory. Make sure that parent of this data directory is not readable by other users on the system (just like /var/lib/private directory).
-- Sunil
OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
