> -----Original Message----- > From: Anthony Ettinger [mailto:[EMAIL PROTECTED] > > I don't know about RPC, but I usually use this syntax > when calling an external command: > > system($cmd) == 0 or die "system @args failed: $?" > > perldoc -f system
Thanks for the reply, but I'm afraid that doesn't address my problem. We need to capture the output from the command as well as be able to access the return code. system() just returns the return code, hence why I said we are using backticks. Sorry if my first explanation wasn't clear about that. > > --- "vega, james" <[EMAIL PROTECTED]> wrote: > > > I'm having a couple interesting issues with > > backticked commands performed > > via RPC[1] calls to another host. The first problem > > is that we will > > sporadically not get back the STDOUT from the > > process. The second problem > > is that, after a certain point, we will stop getting > > back proper return > > codes. It will just return -1. This seems to occur > > after we've fork()ed > > and then called a Perl script from within the fork > > (problems with reentrant > > libraries?). Both of these have occurred with Perl > > 5.8.x. These problems > > have been seen on HPUX, AIX, and Suse. This has > > never occurred on any of > > the Windows hosts that I've used. Thanks in advance > > for any help. This has > > been a real mind boggler. > > > > James > > > > [1]. The RPC service I'm using is the example > > service given in Chapter 13 of > > Advanced Perl Programming. _______________________________________________ Perl-Unix-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
