Well, there are a few cases left to try, don't you think? Run the code via RPC within the client machine. On the server, stub out the client bits and run the subroutine w/o RPC.

Not being shy about making wild guesses in public, I suspect that the second case will turn up a problem. For example, are you sure what the current working directory is when the sub is called via RPC? I'll even guess that your open is failing, causing the <USERS> line to die which probably means that RPC won't be responding anymore.

Oh, and fire your code reviewers if they didn't tell you to check for failure of open! (:

P.S. The quotes around 'USERS' are just fine.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: RPC by tye
in thread RPC by Necos

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.