|
in reply to Remote Execution Perl
You need to have a deamon on the remote server capable of launching the Perl script, and you need to be able to talk to that deamon. SSH deamons, HTTP deamons, HTTPS deamons, FTP deamons and many others match these criteria. It's up to you to choose the one that suits you best. Some are friendlier to firewalls than others (HTTP and HTTPS), some allow interaction (SSH), etc.
|
Re^2: Remote Execution Perl
by linuxfan (Beadle) on Aug 11, 2005 at 19:00 UTC
|
Just remembered that you may also use rlogin, and some people may shoot me in the head for mentioning this. rlogin is obsolete and poses a great security risk! However I've seen rlogin being used in quite a few places (for e.g. DB2 parallel installations use rlogin to execute commands). | [reply] |
|
|
ssh can do everything rlogin can, but it's safer. One should stay away from rlogin unless commanded otherwise, and even then only after a fight.
| [reply] |
|
