Add connecterrlog option to log connect/disconnect script stderr.

[jkroonza]

Closes: #574

[jkroonza]

NOTE: This has only been compile tested, @betulum - could you please confirm if this solves your issue from #574?

[Neustradamus]

@paulusmack: A new PR has been done by @jkroonza, can you look?

[paulusmack]

I would like to hear an explanation of a use case where it is not sufficient for the user to append "2>/some/file" to the connect script.

[jkroonza]

@paulusmack if it's that simple, and @betulum either confirms, or doesn't respond in a sensible time, then I suggest we discard this.

[betulum]

I would like to hear an explanation of a use case where it is not sufficient for the user to append "2>/some/file" to the connect script.

I agree, that approach works fine. Thank you for your hint and sorry for being late with the answer.
@jkroonza, I confirm, you can discard this PR

[Neustradamus]

@betulum: It can be closed?
So, it does not solve #574?

[betulum]

@betulum: It can be closed? So, it does not solve #574?

Yes, I prefer it closing. Redirecting stderr, like proposed by @paulusmack , serves the same purpose