[snip]
>> I essentially need to know that ALL 500k elements were successful,
>> otherwise, I need to know where it broke and where it stopped.
>>
>> This is a billing situation so it has to be accurate. I'd rather ensure
>> (by doing manual double-entry checking) accuracy then having to go
>> thro
Steve Bertrand wrote:
[snipped due to excessive content]
...
[snip]
Tom was probably thinking of Unix, but same principles apply to other
platforms.
It's also worth noting that whatever application you're using to update
the database may well output something useful to STDOUT and it may be a
[snipped due to excessive content]
...
> [snip]
>
> Tom was probably thinking of Unix, but same principles apply to other
> platforms.
>
> It's also worth noting that whatever application you're using to update
> the database may well output something useful to STDOUT and it may be a
> simple st
Steve Bertrand wrote:
> Tom Phoenix wrote:
>>
[snip]
>>
I think you're looking for the program's exit status. Traditionally on
Unix and many similar systems, the exit status is an integer, with 0
meaning "normal exit" and anything else meaning that something went
wrong. That's the value that's
>> I am heavily modifying (re-writing) some Perl scripts that are bundled
>> within the dialup_admin web interface for FreeRADIUS.
>>
>> Eventually I'd like to bring the execution of a few system commands
>> (executing mysql binary and importing an SQL file into it) into Perl,
>> however, for now I
On 12/12/07, Steve Bertrand <[EMAIL PROTECTED]> wrote:
> I am heavily modifying (re-writing) some Perl scripts that are bundled
> within the dialup_admin web interface for FreeRADIUS.
>
> Eventually I'd like to bring the execution of a few system commands
> (executing mysql binary and importing an
