aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-connectivity/openssh/openssh/add-test-support-for-busybox.patch
diff options
context:
space:
mode:
authorRichard Tollerton <rich.tollerton@ni.com>2014-07-16 16:28:32 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-07-19 00:08:49 +0100
commit993405285e547403d5c753adfa91c26c43be13f6 (patch)
tree2b594776c7fb7e2f727d3a163b4c1c8a4717a573 /meta/recipes-connectivity/openssh/openssh/add-test-support-for-busybox.patch
parentf7f3a1fb3855799bb48708f32533e93e336e6995 (diff)
downloadopenembedded-core-contrib-993405285e547403d5c753adfa91c26c43be13f6.tar.gz
openssh: use pidfile in initscript
Stopping sshd must only kill the listening (top-level) daemon; it must not stop any other sshd process, because those are forked ssh connections which may include e.g. the connection that called /etc/init.d/sshd stop. This initscript uses "start-stop-daemon -x <exe>" for starting/stopping. When that is provided by busybox, this behavior is broken: `/etc/init.d/sshd stop` stops *all* sshd processes. This was caused by a fix to busybox 1.20: 17eedcad9406c43beddab3906c8c693626c351fb "ssd: compat: match -x EXECUTABLE by /proc/pid/exe too". The fix is to use a pidfile. All initscripts in upstream openssh do this, as does dropbear. Acked-by: Gratian Crisan <gratian.crisan@ni.com> Acked-by: Ken Sharp <ken.sharp@ni.com> Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity/openssh/openssh/add-test-support-for-busybox.patch')
0 files changed, 0 insertions, 0 deletions