On 4/24/24 06:50 AM, Tom Hughes wrote:
On 24/04/2024 02:28, Xose Vazquez Perez wrote:
# mkdir /etc/systemd/system/httpd.service.d/
# vi /etc/systemd/system/httpd.service.d/override.conf
[Service]
ProtectHome=false
Better than just opening up whole trees again would
be to use ReadWritePaths=
On 24/04/2024 02:28, Xose Vazquez Perez wrote:
# mkdir /etc/systemd/system/httpd.service.d/
# vi /etc/systemd/system/httpd.service.d/override.conf
[Service]
ProtectHome=false
Better than just opening up whole trees again would
be to use ReadWritePaths= to specify which paths should
be allowed
On Tue, Apr 23, 2024 at 08:52:18PM -0400, Steven A. Falco wrote:
> I upgraded to F40, and suddenly an apache cgi script that was working
> perfectly in F39 (and earlier) is giving me a "Read-only file system" error
> when trying to write data into a file.
>
> The directory where the cgi is tryin
Steven A. Falco wrote:
I upgraded to F40, and suddenly an apache cgi script that was working perfectly
in \
F39 (and earlier) is giving me a "Read-only file system" error when trying to
write \
data into a file.
The directory where the cgi is trying to write is owned by apache:apache, and
it
Steven A. Falco wrote:
> I upgraded to F40, and suddenly an apache cgi script that was working
> perfectly in F39 (and earlier) is giving me a "Read-only file system"
> error when trying to write data into a file.
>
> The directory where the cgi is trying to write is owned by
> apache:apache, and
I upgraded to F40, and suddenly an apache cgi script that was working perfectly in F39
(and earlier) is giving me a "Read-only file system" error when trying to write
data into a file.
The directory where the cgi is trying to write is owned by apache:apache, and
it is mode 777. The file the c
