Bug#756903: Boot hangs for 90s and drops into rescue shell if filesystems unavailable

Michal Suchanek hramrach at gmail.com
Tue Feb 3 23:09:13 GMT 2015


Package: systemd
Version: 215-10
Followup-For: Bug #756903

Hello,

why is it such a problem to put sshd on the list of services to start on
failure?

Surely it should only start if it was enabled on the system in the first
place.

However, starting sshd should not cause anything disastrous when some of
your disks are missing. At worst you would be unable to log in because
some of the disks are actually needed for that.

Thanks

Michal

-- Package-specific info:

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (171, 'unstable'), (151, 'experimental'), (121, 'precise-updates'), (121, 'precise-security'), (121, 'precise'), (101, 'stable'), (101, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl             2.2.52-2
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-58
ii  libacl1         2.2.52-2
ii  libaudit1       1:2.4-1+b1
ii  libblkid1       2.25.2-4.1
ii  libc6           2.19-13
ii  libcap2         1:2.24-6
ii  libcap2-bin     1:2.24-6
ii  libcryptsetup4  2:1.6.6-4
ii  libgcrypt20     1.6.2-4+b1
ii  libkmod2        18-3
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     215-10
ii  mount           2.25.2-4.1
ii  sysv-rc         2.88dsf-58
ii  udev            215-10
ii  util-linux      2.25.2-4.1

Versions of packages systemd recommends:
ii  dbus            1.8.12-3
ii  libpam-systemd  215-10

Versions of packages systemd suggests:
ii  systemd-ui  3-2

-- no debconf information



More information about the Pkg-systemd-maintainers mailing list