when sshd is bind to a not valid ip (not valid anymore), the sshd-init-script in /etc/init.d starts up without an error, but sshd isn't started. i recognized this while binding sshd to my wlan card-adress, as it wasn't there i hit this bug. manually deleting sshd in /var/lib/init.d/started, changing sshd_config and starting sshd (via /etc/init.d/sshd start) solved it for me. Reproducible: Always Steps to Reproduce: 1. change bind to a non-valid ip-adress in sshd_config 2. /etc/init.d start 3. Actual Results: sshd doesnt show up. stopping, starting or restarting sshd wasn't possible. (at least via /etc/init.d/sshd ;). Expected Results: error while starting sshd Gentoo Base System version 1.4.16 Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r1, 2.6.10-cko3 i686) ================================================================= System uname: 2.6.10-cko3 i686 Intel(R) Pentium(R) III Mobile CPU 866MHz Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 15 2005, 01:55:06)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer -mfpmath=sse,387 -msse -mmmx" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer -mfpmath=sse,387 -msse -mmmx" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.tu-clausthal.de/pub/linux/gentoo http://gentoo.oregonstate.edu" LANG="de_DE.UTF-8" LC_ALL="de_DE.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/home" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X aalib acpi alsa apache2 apm avi bash-completion berkdb bitmap-fonts cdr crypt cups doc emboss encode ethereal fam ffmpeg foomaticdb fortran gd gdbm gif gtk gtk2 imlib insecure-drivers ipv6 java jpeg junit ldap libg++ libwww mad makecheck mikmod mmx mono motif mozilla mp3 mpeg mysql ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline real sdl slang spell sqlite sse ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts unicode vorbis x86 xml2 xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, LINGUAS
from what i can tell by looking at the issue quickly, sshd itself will exit properly even with a sshd_config file with a bad ip address in it that means we cant really tell from the init script if a configuration such as this will cause problems ... it would take patching of the source code of sshd to resolve this 'properly' which means an upstream change is needed
