Actually, you might want to see the manpages for ssh-keygen and perhaps ssh-agent. Basically you create an RSA key with no password (or use ssh-agent to keep the decrypted key in memory for your process), then run your script without having to deal with the password prompt at all. You'll be using key authentication instead of password auth.
Update: You might also look at Expect, but using a key is generally better than keeping passwords around in crontabs and/or scripts.
--isotope
| [reply] |
Ok, based on a brief glance at the recommended manpages, that will probably solve the problem.
For curiosity's sake (and in case it doesn't), Anyone want to take another potshot at this?
| [reply] |
| [reply] |
merlyn already offered a solution, but in this case I can say that it does solve the problem. I have a lot of programs which use this to great effect, saving a lot of headaches. (As a security note, why bother having a password for the account at all?:-)
| [reply] |
You can find a description on how to set automatic authentication via SSH in
GRID::Machine::perlparintro.
Once is set you can use GRID::Machine in your script
to have a Perl interpreter running under your control in the
remote side
| [reply] |