[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Tracking an Error within a Perl script
- Subject: RE: [cobalt-users] Tracking an Error within a Perl script
- From: "Ian" <ian@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu Nov 7 11:25:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Hi all,
> Another way to debug a perl script is to put the following
> command in the second line of the perl script after #!/usr/bin/perl
>
> use CGI::Carp qw(fatalsToBrowser);
The -w and the above Carp command did the job nicely.
Using that I went through each of the paths and changed them to full paths
including:
/home/sites/sitexx/web/etc etc
And now it all works...
I take it that by using the full path as like this is not a security problem is
it and quite normal.
Thanks again Gerald/Brian for the assistance, much appreciated.
Ian