Hi is there any documentation on the new reexec mechanism in sshd? (didn't find find much about it here on the list) Background of this question: I added a session numbering to our internal version to help keeping all log messages of one client connection together. In 3.9p1 the current number gets lost when the sshd is restartet in the reexec mechanism. I'd like to find a way to pass the number to the new process (maybe I'll add a cmd line option) instead of disabling reexec. Frank
you have to extend {send,recv}_rexec_state in sshd.c On Wed, Sep 01, 2004 at 11:43:31AM +0200, Frank Mohr wrote:> I'd like to find a way to pass the number to the new process > (maybe I'll add a cmd line option) instead of disabling reexec.
Maybe Matching Threads
- Re: [PATCH nbdkit 3/5] vddk: Miscellaneous improvements to reexec code.
- Re: [PATCH nbdkit 3/5] vddk: Miscellaneous improvements to reexec code.
- [PATCH nbdkit 3/5] vddk: Miscellaneous improvements to reexec code.
- sshd "getpeername failed: Transport endpoint is not connected" error
- [PATCH nbdkit 2/5] vddk: Move reexec code to a new file.