Mark.Donaldson AT cexp DOT com wrote:

> bperror -S 73
> bpstart_notify failed
> The bpstart_notify script returned a nonzero exit code.
> 
> You might add some logging to the script.
> 
> Right near the top, add:
> 
> exec >/tmp/bpstart.out 2>&1
> 
> and you can capture all the output & hopefully the error message.
> 
> I suspect, though, since it runs OK by hand, that it's an environment
> problem.  NB is going to use a different shell that you do.  I usually find
> these are PATH errors - some command isn't being found.

I found that bpstart_notify was only getting 4 of 6 arguments.
I'm still running 3.4 BTW, and it seems it only gets the client,
class, schedule, and type for args.  I had to comment out the
number of args checking to see this and not have it fail.

-- 
Dan