On 2025-08-26 17:40, Ron via Talk wrote:
Ron via Talk wrote on 2025-08-26 14:23:
After much debugging I tracked the problem down to a configuration file lighttpd installs for systemd, namely /lib/systemd/system/ lighttpd.service which is symlinked by /etc/systemd/system/multi- user.target.wants/lighttpd.service.
The lighttpd developers added a configuration parameter (ProtectHome=read-only) that completely disables cgi-bin access.
I forgot to say, that's some good detective work.
### Editing /etc/systemd/system/postgresql@14-main.service.d/ ProtectHome.conf
And on this topic, I forgot to say that files in /etc/systemd are meant to override the default files in /lib/systemd.
So replacing the symlink in /etc/systemd with a copy of the orig file and making changes there is another option that will persist between re- installs.
(Unless un-installed with --purge, maybe?)
But the overrides / drop-ins are a nifty way to make changes to defaults that can be easily moved between machines, etc. ------------------------------------ Description: GTALUG Talk Unsubscribe via Talk-unsubscribe@lists.gtalug.org Start a new thread: talk@lists.gtalug.org This message archived at https://lists.gtalug.org/archives/list/ talk@lists.gtalug.org/message/GVUREPGIJUSTDN7FBAYL6BCEQR6OMTBO/
Thanks Ron, I tried to follow your original instructions. I think that, because I fixed the problem in the spring by editing a file systemd file directly, the systemd edit process failed on me, going very strange. But after trying to repair systemd for a while I just directly created a /etc/systemd/system/lighttpd.service.d directory containing an override.conf which set ProtectHome=no. That worked fine. PS: systemd is really sticky. Uninstalling and reinstalling lighttpd was not enough to reset its state on lighttpd. Google suggested I do a complete purge of the lighttpd package, including configuration to get systemd cleaned up. -- Michael Galea