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. On 20 February 2012 10:36, Tom Evans <[email protected]> wrote: > Again, unlikely. Computer programs, given the same inputs, will > generally produce the same outputs. Probably you are not invoking the > script with the same environment - if you are invoking as a CGI, that > includes all headers, cookies, user agent strings etc. > -- Steve Swift http://www.swiftys.org.uk
