Perhaps you could alias a function that pipes like tee, and checks for errors. Like this:
alias myfunc "errorchecker >& /dev/null"
[command] | myfunc
What it does with those errors is up to you, though your main options are "print them" (in which case, just don't redirect stderr), "log them for fetching" (and write a little command to access & manage the failure reports), or "email them to yourself".
I guess basically what I'm getting at is, look at distributed processing backends such as LSF or GRD for inspiration.
I guess basically what I'm getting at is, look at distributed processing backends such as LSF or GRD for inspiration.
reply