Bug#710755: openssh-server: LSB: Should-Start: network-manager
Package: openssh-server Version: 1:6.2p2-3 Severity: important On systems running network-manager, openssh-server starts too soon. solving this requires adding the follow to the init script's LSB header: # Should-Start:network-manager # Should-Stop: network-manager -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-4-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-server depends on: ii adduser 3.113+nmu3 ii dpkg 1.16.10 ii libc6 2.17-3 ii libcomerr21.42.5-1.1 ii libgssapi-krb5-2 1.10.1+dfsg-5 ii libkrb5-3 1.10.1+dfsg-5 ii libpam-modules1.1.3-9 ii libpam-runtime1.1.3-9 ii libpam0g 1.1.3-9 ii libselinux1 2.1.13-2 ii libssl1.0.0 1.0.1e-3 ii libwrap0 7.6.q-24 ii lsb-base 4.1+Debian11 ii openssh-client1:6.2p2-3 ii procps1:3.3.4-2 ii sysv-rc 2.88dsf-41 ii zlib1g1:1.2.8.dfsg-1 Versions of packages openssh-server recommends: ii ncurses-term 5.9+20130504-1 ii xauth 1:1.0.7-1 Versions of packages openssh-server suggests: pn molly-guard none pn monkeysphere none ii openssh-blacklist0.4.1+nmu1 ii openssh-blacklist-extra 0.4.1+nmu1 pn rssh none pn ssh-askpass none pn ufw none -- Configuration Files: /etc/init.d/ssh changed [not included] /etc/pam.d/sshd changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710755: openssh-server: LSB: Should-Start: network-manager
On Sun, Jun 02, 2013 at 09:48:31AM +0300, Martin-Éric Racine wrote: On systems running network-manager, openssh-server starts too soon. solving this requires adding the follow to the init script's LSB header: # Should-Start:network-manager # Should-Stop: network-manager Why does this matter? Normally, just starting up and creating the listen socket shouldn't require the network to be up, at least with standard configuration; furthermore, we install an if-up hook to restart sshd when new network interfaces come up in order that it can start listening on them if necessary. I'm very reluctant to impose ordering constraints here, as many people specifically want sshd to come up as soon as possible. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
