On Mon, Feb 20, 2012 at 1:16 PM, Steve Swift <Swifty@xxxxxxxxxxxxxx> 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 circumstances. > > So, without a single byte of my code changing (including the shebang; the > file's "last changed" timestamp is usually months in the past), the script > will run happily for months on end, encounter one of these weird "sh" > errors, then go back to working again. > I'll try and make it clearer - Apache *does not* invoke sh, *for any reason*. If sh is being invoked, your script is doing it. If you see sh errors in your error log, then your script is invoking sh incorrectly. Cheers Tom --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx