Something (possibly systemd) creates per user / per process (?) /tmp
directories.
These are actually held in /tmp/systemd-private-*
Gary
On Friday 20 January 2017 15:19:52 Jerry Geis wrote:
> Fun fact... If I echo my data to the same directory as the script is
> located in it works. But it d
The behavior you describe should be normal for any web server, as it is
for Apache, which is what I use. It is a security feature that prevents
malicious attacks on a web server from writing malware anywhere else in
the filesystem and possibly gaining elevated privileges.
On 01/20/2017 10:19
Fun fact... If I echo my data to the same directory as the script is
located in it works. But it does not allow writing to /tmp
I'm good with that.
Thanks,
Jerry
On Fri, Jan 20, 2017 at 9:54 AM, Jerry Geis wrote:
> Hi - Thanks for the reply.
>
> I actually have selinux disabled on this box.
>
Hi - Thanks for the reply.
I actually have selinux disabled on this box.
Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Just a speculation but /tmp is usually world-writable which leads me to suspect
SELinux (or AppArmor with other distros.)
- Original Message -
From: "Jerry Geis"
To: "CentOS mailing list"
Sent: Friday, January 20, 2017 7:29:02 AM
Subject: [CentOS] CentOS 7 httpd
Hi all,
I have a script running in httpd. The script runs fine.
However I want to "echo" some debug information into a file.
The file is never created.
Is there some security thing that has to be enable/disabled to allow a
script in httpd to write to a file?
Thanks,
Jerry
__
6 matches
Mail list logo
