system() needs file system paths, not urls. If your cgi-bin directory is really at /var/www/cgi-bin (for example), then you have to use that path to call the script.

apache might also have problems finding the perl interpreter. You might use the complete path to perl to find out whether that is the problem

I tried this as well with no luck....

system("/usr/bin/perl /cgi-bin/test1.pl");

I think you missed what jethro was saying. /cgi-bin/test1.pl is very unlikely to be a file path to the executable. It implies (though guarantees nothing) that / is your webroot. When you're on the command line, where is test1.pl? That's what you're after. You should also be checking the system return and using the multi-arg call. See perldoc -f system or search in here for more.

I'd try using the FindBin module. This means that even if there's weird things going on with chroot and paths being rewritten, you should hopefully get the other script invoked:

use FindBin qw($Bin);

system($^X, "$Bin/test.pl");
[download]

This is assuming that your test1.pl is in the same directory as your calling script. If you're wondering what $^X is, it's the full path to your perl interpreter, which means the above line should work, even if Perl is not in your path.

I'm using the two-argument version of system, which means that if your host is a Unix-flavoured system, it should avoid the shell (and hence any problems where your script may not have a shell to run).

It's also recommended that you check the return value from system(), so if something does go wrong, you know about it. I personally use IPC::System::Simple for this task, which automates most of the checking and diagnostics, but being Perl there's more than one way to do it.

All the best,

To call/invoke/run a Perl script from another Perl script you can also do something like:

# call_another_script.pl
use strict;
use warnings;

do {
    local @ARGV;

    @ARGV = ("Hello", "World!");
    eval { require "script_to_call.pl" };
};

print "\nOriginal args:\n";
for my $arg (@ARGV) {
    print "$arg\n";
}
[download]

# script_to_cal.pl
use strict;
use warnings;

print "script_to_call.pl args:\n";
for my $arg (@ARGV) {
    print "$arg\n";
}
[download]

hi all, I need to execute perl script(script_to_call.pl) on my remote location can I do it in same way (with @ARGV)? This below one not parse @ARGV:

do {
    local @ARGV;

    @ARGV = ("$OldTime","$NewTime","$WLSP/CDSServer11.log");
    eval { system("ssh -o stricthostkeychecking=no $WLS './script_to_c
+all.pl'");
        };
};
[download]

Instead of asking a question in a 4 year old thread, you should open a new thread. Your problem is also different to the problem addressed in this thread. See safely passing args through ssh for ideas.

I'll play devil's advocate and guess that the logfile does not have write access given to the user which the webserver runs as (http, apache?). Have you run test1.pl as a cgi script, through the web browser?

Insert debugging print messages into the test1.pl script. This would verify if the script is not being executed.