Do you have to use your script - far more efficient would be something along the lines of...
  1. Put the file on a file system on a local host that is/can be exported (via NFS) to all intended remote client machines (to save copying time)
  2. NFS mount(1M) the exported file system on each remote client machine
  3. Run the install on each remote client machine
The latter 2 steps could be achieved in parallel, in sh(1), in a manner similar to...
for M in M1 ... Mn ; do rsh $M "nohup mount <source mc>:/<export fs> /import/fs ; /<import + fs>/install " & done
I'm inferring that, since you have permissions to install on the remote machines, you have permissions to run mount(1M) - and to create the mount point(s) on the remote client machines (if needed).

A user level that continues to overstate my experience :-))

In reply to Re: net::telnet problem by Bloodnok
in thread net::telnet problem by tprizler

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.