Bug#845186: systemd: does not respect ctrl-c running into timeout when starting or stopping services

Martin Steigerwald Martin at Lichtvoll.de
Mon Nov 21 08:58:57 GMT 2016


Package: systemd
Version: 232-5
Severity: normal

Dear Martin, dear Michael, dear Maintainers,

as I added a removable LUKS crypto device to fstab like in

/dev/mapper/someluksdevice /mnt/somemountpoint      btrfs           noatime,autodefrag,compress=lzo          0       0

I forgot to add "noauto".

Consequently systemd ran into a timeout of 90 seconds that was not
interruptible.

On the other hand atopacctd from experimental right now does not respond to
SIGTERM properly at the moment, again leading into a 90 seconds timeout,
that again is not interruptible with Ctrl-C.


Actual results

Pointless waiting. I know the action is not going to succeed. I know this
*better* than systemd. Frustration cause I get the impression systemd tries
to control me while I think it should be the other way around.


Expected results

When I press Ctrl-C when systemd runs into a timeout, I expect systemd
to execute my command as soon as possible. Cause actually I know better
than systemd in that cases and waiting for the completion of the timeout
is pointless.

I have some understanding that systemd may not allow Ctrl-C in all circum-
stances, since it may be possible that someone tries to hack the boot
process by just pressing Ctrl-C, but when systemd notices that it runs
into a timeout and displaying so I expect it to give an option to tell it
to stop waiting pointlessly.


I think this is an upstream issue. Feel free to forward it. I don´t feel
like arguing with systemd upstream myself given my past experiences on
systemd developer mailinglist, please respect that.

Thank you,
Martin

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages systemd depends on:
ii  adduser         3.115
ii  libacl1         2.2.52-3
ii  libapparmor1    2.10.95-6
ii  libaudit1       1:2.6.7-1
ii  libblkid1       2.29-1
ii  libc6           2.24-5
ii  libcap2         1:2.25-1
ii  libcryptsetup4  2:1.7.3-2
ii  libgcrypt20     1.7.3-2
ii  libgpg-error0   1.25-1
ii  libidn11        1.33-1
ii  libip4tc0       1.6.0+snapshot20161117-1
ii  libkmod2        23-1
ii  liblz4-1        0.0~r131-2
ii  liblzma5        5.2.2-1.2
ii  libmount1       2.29-1
ii  libpam0g        1.1.8-3.3
ii  libseccomp2     2.3.1-2.1
ii  libselinux1     2.6-3
ii  libsystemd0     232-5
ii  mount           2.29-1
ii  util-linux      2.29-1

Versions of packages systemd recommends:
ii  dbus            1.10.12-1
ii  libpam-systemd  232-5

Versions of packages systemd suggests:
ii  policykit-1        0.105-17
ii  systemd-container  232-5
ii  systemd-ui         3-4

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.125
ii  udev             232-5

-- Configuration Files:
/etc/systemd/resolved.conf changed [not included]

-- no debconf information



More information about the Pkg-systemd-maintainers mailing list