BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] apache
- Subject: [Discuss] apache
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Sat, 2 Nov 2024 09:11:22 -0400
- In-reply-to: <ZyFwQau_YgcrIbrC@deneb2>
- References: <ZyFwQau_YgcrIbrC@deneb2>
On Tue, 29 Oct 2024 19:31:13 -0400 dan moylan <jdm at moylan.us> wrote: > sorry, i forgot to mention at the outset i disabled selinux. Double-check that to be sure nothing has quietly re-enabled SELinux. Otherwise, the directory being written needs to be writable by the UID or GID doing the writing, and all parent directories up to / need to be readable by this UID or GID. I think this is not a good idea. System services shouldn't be writing into users' home directories. If you want logs to be visible via /home then I think the sanest thing is to let Apache write its logs in /var/log/apache or /var/log/httpd (whichever), and then either use a symbolic link or bind mount to make it visible via /home/${USER}/log. -- \m/ (--) \m/
- Next by Date: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Next by thread: [Discuss] Wireguard and Traveling and Network Overlaps oh my!
- Index(es):