Greetings!

I have a weird problem:
In the last 2-3 weeks Apache server upon calling my CGI application started to write this to a log file:

[Wed Feb 15 17:09:32 2006] [error] [client 192.168.14.21] script not f +ound or unable to stat: /some/path/undefined, referer: http://test-se +rver/cgi_app.pl
Of course program '/some/path/undefined' does not exist, nor any invocation of a program of that name in my source code (nor in apache config files).
Anywhere!

So I made a little program named 'undefined' and placed it in /some/path. This program appends to a /tmp/some_file.log time of call and arguments passed to a program. After a few execution of a CGI program I get execution times in that file (meaning @ARGV is empty). So now I don't have nasty lines in apache log files :-)

Any hints of what could possibly generate such behaviour in a CGI application?


In reply to invocation of a ghost file by arkturuz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.