> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of MARTIN MOSS
> Sent: Thursday, August 26, 2004 12:11 PM
> To: [EMAIL PROTECTED]
> Subject: [Perl-unix-users] taking strings and printing them
> to a file which is itself a perl file
>
> All,
>
> Ho
t 20, 2004 11:00 AM
> To: vega, james
> Cc: [EMAIL PROTECTED]
> Subject: Re: RE: [Perl-unix-users] Odd problems from shell
> commands run via RP C service
>
>
> Is it possible that the process is being killed externally.
> If that happens, the output using backticks might
tried:my $command_output = `some_system_command_here`;
#look carefully here ... it is <<`>>, not
<<'>>print "output:\n" . $command_output;Good
Luck,Dragos CIULICA.On Fri, 2004-08-20 at 16:33, vega, james
wrote:
> -Original Message-
> F
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 cl
Title: Odd problems from shell commands run via RPC service
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
