On Mon, Feb 20, 2012 at 4:16 PM, Phil Smith wrote:
> On Mon, Feb 20, 2012 at 8:54 AM, Tom Evans wrote:
>> On Mon, Feb 20, 2012 at 1:16 PM, Steve Swift wrote:
>>> Ah, but the "sh" error means that my code never starts executing. If the
>>> very first line of my code were to get executed, then the
Do any of the GET requests in your access log correspond with CGI scripts
which might run for a long time? I presume that the access log entry
corresponds to when the script starts, not when it ends. The "sh" error
messages may thus occur minutes after the corresponding GET entry in the
access log.
On Mon, Feb 20, 2012 at 8:54 AM, Tom Evans wrote:
> On Mon, Feb 20, 2012 at 1:16 PM, Steve Swift wrote:
>> Ah, but the "sh" error means that my code never starts executing. If the
>> very first line of my code were to get executed, then the error message
>> would come from the error handlers in m
Thank you for your persistence, which has paid off, and conquered my
obtuseness.
So, apache doesn't invoke "sh". Neither does my code, explicitly. But when
my script invokes a host command, the interpreter just hands the command to
the default execution environment, which in this case is "sh".
I
On Mon, Feb 20, 2012 at 1:16 PM, Steve Swift wrote:
> Ah, but the "sh" error means that my code never starts executing. If the
> very first line of my code were to get executed, then the error message
> would come from the error handlers in my code, but nothing in my code
> executes under these ci
Ah, but the "sh" error means that my code never starts executing. If the
very first line of my code were to get executed, then the error message
would come from the error handlers in my code, but nothing in my code
executes under these circumstances.
So, without a single byte of my code changing (
On Sat, Feb 18, 2012 at 4:30 PM, Steve Swift wrote:
> I get entries like this in my error log. They are extremely sporadic, and
> because the access rate is low on our server, it is easy to find the CGI
> script that was being accessed. In all cases, it is one which hasn't changed
> in months, and
I get entries like this in my error log. They are extremely sporadic, and
because the access rate is low on our server, it is easy to find the CGI
script that was being accessed. In all cases, it is one which hasn't
changed in months, and has seen plenty of use in the intervening period,
without pr
On Sat, Feb 18, 2012 at 7:10 AM, Eric Covener wrote:
> On Sat, Feb 18, 2012 at 12:00 AM, Phil Smith wrote:
>> I'm running Apache/2.2.3 (CentOS) which is the latest version
>> available for CentOS5.
>> I'm noticing the following in my error logs:
>> sh: -c: line 0: unexpected EOF while looking for
On Sat, Feb 18, 2012 at 12:00 AM, Phil Smith wrote:
> I'm running Apache/2.2.3 (CentOS) which is the latest version
> available for CentOS5.
> I'm noticing the following in my error logs:
> sh: -c: line 0: unexpected EOF while looking for matching `"'
> sh: -c: line 1: syntax error: unexpected end
I'm running Apache/2.2.3 (CentOS) which is the latest version
available for CentOS5.
I'm noticing the following in my error logs:
sh: -c: line 0: unexpected EOF while looking for matching `"'
sh: -c: line 1: syntax error: unexpected end of file
They usually arrive in groups of 2-10 such messages;
11 matches
Mail list logo
