> print pass1 siginfo messages to stdout, rather than to stderr I guess that would, together with the recent rc.log logging, explain it. > does that fix the misbehaviour you saw? I can't test right now, but thanks for (probably) fixing it anyway.