On Sun, May 22, 2016 at 6:03 AM, Nick Kew wrote:
[cut]
Nick, thanks for your help, but in the end I solved.
It was an issue with the permissions, that involved the suEXEC
mechanism. I didn't know about suexec and I found out that some
relevant information goes in the system log instead of the ap
On Sun, May 22, 2016 at 6:03 AM, Nick Kew wrote:
> On Sun, 2016-05-22 at 04:05 +0100, Alessandro Re wrote:
>
>> #!/usr/bin/sh
>
> Is that a typo or an unusual filesystem?
I don't know if it's unusual or not, but it's not a typo :)
$ ll /usr/bin/sh
lrwxrwxrwx. 1 root root 4 Jan 11 11:02 /usr/bin/
On Sun, 2016-05-22 at 04:05 +0100, Alessandro Re wrote:
> #!/usr/bin/sh
Is that a typo or an unusual filesystem?
Does your script run from the commandline
(as "/path/to/test.cgi", not as "sh test.cgi")?
--
Nick Kew
-
To unsu
Dear community,
I do not like to cross-post, but I cannot find a solution to this
problem (yes, I searched). The discussion started at [1], but I am
seeking help also here, because I cannot get what is wrong and I
cannot understand how to get more detailed error logs - so I thought
that a speciali
