I have a lot of work that needs to be dont in vmware, so i thought i'll keep that file separate(5.005) and have another file for XML-RPC(5.8.) as u said. i forked and execed and loaded vmware into child process. no how do i use pipes for communication, (pipe File Descriptor becomes invalid) or can i use socketpair...
any example. ? On 8/6/07, vishnu <[EMAIL PROTECTED]> wrote: > > great, > I'll try it and get back on this.. > I'm really glad u shawed me a way.thanks, :) :) :) > > will update u on the developments > regards, > vishnu > > On 8/6/07, Chas Owens <[EMAIL PROTECTED]> wrote: > > > > On 8/6/07, vishnu <[EMAIL PROTECTED]> wrote: > > > hi, > > > VMware while starting uses an exec call to execute its own version > > of > > > perl (5.005), But i need to use XML-RPC which does not come with > > VMware. > > > When i try to import or use XML-RPC like (require RPC::XML;) i got an > > error > > > saying the .pm file was missing.. so i went and added default @INC > > while > > > using exec for vmware.... but there's a version problem. > > > > > > Error was : Can't modify subroutine entry in scalar assignment at > > > /usr/share/perl/5.8/subs.pm line 3, near "'1.00';" > > > > > > the actual line in subs.pm is (our $VERSION='1.00'); > > > > > > > > > Now is there any version of XML-RPC that supports VMware . > > > > > > can anyone help me on this regard on what went wrong...... :( , > > snip > > > > What is going wrong is the our function does not exist until version > > 5.6. You are basically hosed. This is the downside to using such an > > old version of Perl. Here are your options as I see them, in order of > > preference: > > > > 1. if you are paying for support file a ticket with VMWare; it is > > unacceptable that they are still using 5.005, they need to upgrade to > > 5.6.2 at least (most of modern Perl will run on 5.6.2) or to release > > versions of their binary modules that can link with modern Perl (not > > likely as they would need to support umpteen different distributions > > of Perl). > > 2. Write your code as co-processes, one running under 5.8 and a forked > > copy running under 5.005. Use IPC to pass information between them. > > 4. Use the command line utilities instead > > 3. Write the smallest possible code around the VMWare stuff and call > > it from another script running under 5.8 > > 5. hack the modules you need to work under 5.005. > > > > You might also want to read the VMWare support boards. It is unlikely > > you are the first person to run into this class of problem. > > > > > > -- > Vishnu, > cell:99944 75599 > > "if you don't make mistakes, > chances are you are not stretching yourself." > -- Vishnu, cell:99944 75599 "if you don't make mistakes, chances are you are not stretching yourself."
