Given that not much widely used software uses ONC RPC still (at least I can't really think of anything that I'd call "widely used" save NFS off the top of my head) that's not surprising. That's not to say nobody uses it for some internal application, but things like several security holes in rpc.portmapper and what not put an end to widespread use on the Internet as a whole, IMSMR.

If there's a wrapper library available for the protocol you need you probably can use that via Inline::C; that's also probably going to be your best starting point to reimplement an ONC RPC module yourself (which I'm betting is what you're going to wind up doing, unfortunately). You should also look and see if there isn't an interface available in a more "up to date" RPC protocol such as SOAP, XML-RPC, or CORBA.

Update: Just thought of what'd be a tremendous kludge, but you might look through the source of old Linux distributions to see if you couldn't find an implementation of the ONC RPC libraries that's source compatible with what's on CPAN and then see if you can get those to compile instead of using what ships with your OS. But again, that'd be a tremendous kludge and possibly more effort than just rewriting your own perlrpcgen from scratch.

In reply to Re: RPC ONC by Fletch
in thread RPC ONC by pierre31

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.