On Mon, 2008-05-19 at 22:08 +0800, Jeff Peng wrote: > On Mon, May 19, 2008 at 10:01 PM, Matthew Whipple > <[EMAIL PROTECTED]> wrote: > > > > It sounded as though he wanted to run the script on the Linux machine, > > not the server... > > That was maybe not correct. > Given the case that he say something like this in his script: > > open $pwd, "/etc/passwd" or die $!; > > This will open the linux's password file, not the solaris's.
That would depend upon which side that command was executed. Keep in mind that he had mentioned a script that would iniate the SSH connection from the Solaris computer and could retrieve data from that computer which could then be passed over the connection. I unfortunately no longer have the original message and don't have time to find it, but I had noticed that one of the problem modules he was having was DBI so I was supposing he was looking to store login information in a DB. In that case he would be able to gather login information on the "SERVERK" computer before initiating the SSH connection and passing the information to a script which would handle any functionality not presently supported on SERVERK (not to be confused with permission). The only person to answer this is the OP, and he may not if the alternative module installation prefix works for him. > > If that was really he wanted originally, then using Net::SSH::Expect > has no problems. > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
