esolm has asked for the wisdom of the Perl Monks concerning the following question:

Oh wise one,

I have 2 servers running win 2000, both have perl installed. How do I have server 1 call server 2 and have server 2 run a perl script. Note I don't want to use server 1 to run the script I want to use the 2nd server's cpu etc.

Thanks for the help,

Eli

Replies are listed 'Best First'.
Re: Win 2000 Perl Question
by John M. Dlugosz (Monsignor) on Jun 19, 2001 at 01:59 UTC
    Use COM, either by making it a "script component" or using ActiveState's server maker from their dev kit. Or, use a remote shell (unrelated to Perl). Or, have the script, already running, listen for a signal on a socket or named pipe and GO when the client tells it.
(tye)Re: Win 2000 Perl Question
by tye (Sage) on Jun 19, 2001 at 10:42 UTC

    I'd just go with standard TCP/IP (sockets) servers and clients. Simple, portable, well documented and supported.

    My second choice should probably be the RCmd service and client from the WinNT resource kit (though I haven't used these with Win2K).

            - tye (but my friends call me "Tye")
Re: Win 2000 Perl Question
by TGI (Parson) on Jun 19, 2001 at 03:04 UTC

    You could also use apache and mod_perl or CGI. This will give you a very flexble platform to work from. Of course it'll eat a bit more ram than the other options.

    Once apache is running and serving your scripts (or wrappers for your scripts) as CGI, you can trigger them with any http client (such as IE or something whipped up in LWP).


    TGI says moo