I'd go with Net::SSH and Net::Telnet for the login processes, as others have pointed out.

For file copies, I would consider rsync or cfengine in a pull setup. You can signal the pull on the client so it acts like a push, and it has the advantage that if you update the configuration you can have it automatically propagate. You can do this based on machine classes (e.g. machine "zorro" is in class "bandits") so you know exactly what machines are going to copy your RSA key, for instance. Logs are kept by rsync and cfengine, but you'll find that things will Just Work, and logs will be used very rarely. I can't recommend cfengine enough for the kind of administration you are doing.

Ted

In reply to Re: Login Script by tzz
in thread Login Script by /dev/null

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.