dknf

[brian at aljex.com]

Quoting brian at aljex.com:

> In all cases the field I want to update does get updated the way I want, and
> no
> other fields (such as the neighboring or any other record) get screwed up,
> and
> so if I set PFMBTO=1 and direct stdout & stderr to null (it's a background
> process triggered by receiving email) then I actually get what I want.

Also just verified I really get every little thing I wanted, including even my
desired exit errorlevel is set, even if I asked for exit "0", and then got the
dknf, non-interactively passed by PFMBTO=1, the resulting exit status of the
rreport command is still 0. When I ask for exit "1" I get it too.

Not sure what to think about that.
Clearly filepro thinks there was an error, so, I think it should not exit with
some errorlevel regarless what my processing asked for since rreport itself had
a problem even if my processing running within rreport didn't.

But in this case, the code is all working exactly as I want and I might want to
use the exit status to detect errors at the higher level, like bad data, and
make decisions back in the parent shell script based on that, so I'm just as
happy that it honors my exit command above it's own feelings in this particular
case.

bkw

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.