The appropriate solution will vary dependant upon what type of system (Win32/*nix/other) the commands originate from and how it is connected to the remote systems (LAN/WAN/inet).
It would also help to know what type of commands and processes you intend to run remotely.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
Hooray!
| [reply] |
| [reply] |
I don't know about any modules specifically, but off the top of my head, you might look in the direction of rsh on Windows. Some Windows servers do support the command, you might just have to see if you can do it. Of course your mileage may vary :-)
"Ex libris un peut de tout"
| [reply]
[d/l] |
This might be a stretch, but if you want your code to be nice and UNIX-ish, you could possibly run an SSH server on your Windows machine. Sure, it's not the most Microsofty solution, but it would allow you to use something like Net::SSH and then Migration away from Windoze would be easier :)
Using the Windows telnet daemon is doable, but you will be sending plaintext passwords...avoid telnet!
Other options might be to write a daemon process for the other machine, using something like XML::RPC or some other RPC module. Whatever you do, don't forget encryption and authentication!
| [reply] |
That's a good point. I just happened to recall seeing the rsh listed in the Windows NT in a Nutshell from O'Reilly. I saw it, played with it for about 5 minutes then put it aside :-)
"Ex libris un peut de tout"
| [reply]
[d/l] |