Thank you ikegami, now tis clear to me what the server error log mean and really i didnt knew up until now that iam supposed to specify custom error logs, i though server was setup in a way to provide fixed error messages.
As for the Carp module i'm already using it in all my perl files, including index.pl, so i dont have to log to cpanel every time to check the error log.
it seems to me though that the runtime of index.pl never reaches the stage of carp module. which is my 2nd line in row, because if it did i would get a proper perl error message. So i still dont see why iam gettign these error messages, which as you say are safe to ignore, and why my script dies instanly without some king of perl error message.
When something like this happened to me *locally* it was because i didnt had a proper shebang constructor, sicne iam on a vista machine, because i uplaod to a unix one. When i fixex that it worked and gave me perl error messages, but in this case the shebang constructo is correct, so then why it aint producing perl error messages? Does the script try to run at all? anf if yes why die instantly?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.