That's an idea. I'll play around and see what happens with the output when
I manually kill the process. I would hope Perl would still get the output,
but we'll see.
> -Original Message-
> From: David Greenberg [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 20, 2004 11:00 AM
> To: vega
Is it possible that the process is being killed externally. If that
happens, the output using backticks might be lost while some or all of
the output will still be written to a file. Maybe it's something along
these lines?
-David
- Original Message -
From: vega, james <[EMAIL PROTECTED]
Title: Message
That's
what we're doing. As I said, it's only sporadically that these commands
don't return STDOUT. For the most part, they work, but sometimes we have
problems. One way that we've worked around the STDOUT problem is by
redirecting STDOUT to a file and then reading back the
> -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 d
It all depends on exactly what the script is doing and the exact specs
of the V100 or Blade2500 that you're getting, but I have worked on
both and would guess you're probably looking at drastic improvement.
When I upgraded from an Ultra10 to a Blade1500, I everything was
overwhelmingly faster (not
Dear All,
I am working on a very low end machine Ultra10. For some reasons, I need to
run a Perl script on 900-1000 files in a sequential manner, almost on daily
basis. This process takes lot of time. I am thinking of changing my
workstation. I think V100 Server or Sun Blade 2500 would be the bette
