Your message dated Sat, 31 Aug 2019 00:34:32 +0200
with message-id <[email protected]>
and subject line Re: Bug#910377: Inhibit reboot/shutdown if dpkg is running
has caused the Debian Bug report #910377,
regarding Inhibit reboot/shutdown if dpkg is running
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
910377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910377
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 239-10
Severity: wishlist
Hi,
Not sure if this should be reported here or in dpkg
Shouldn't it be intresting to add a hook in dpkg to inhibit the
reboot/shutdown of the machine while packages are being
updated/installed?
Kind regards,
Laurent Bigonville
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.13-8
ii libaudit1 1:2.8.4-2
ii libblkid1 2.32.1-0.1
ii libc6 2.27-6
ii libcap2 1:2.25-1.2
ii libcryptsetup12 2:2.0.4-2
ii libgcrypt20 1.8.3-1
ii libgnutls30 3.5.19-1+b1
ii libgpg-error0 1.32-1
ii libidn11 1.33-2.2
ii libip4tc0 1.6.2-1.1
ii libkmod2 25-1
ii liblz4-1 1.8.2-1
ii liblzma5 5.2.2-1.3
ii libmount1 2.32.1-0.1
ii libpam0g 1.1.8-3.8
ii libseccomp2 2.3.3-3
ii libselinux1 2.8-1+b1
ii libsystemd0 239-10
ii mount 2.32.1-0.1
ii procps 2:3.3.15-2
ii util-linux 2.32.1-0.1
Versions of packages systemd recommends:
ii dbus 1.12.10-1
ii libpam-systemd 239-10
Versions of packages systemd suggests:
ii policykit-1 0.115-1
ii systemd-container 239-10
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.132
ii udev 239-10
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 5 Oct 2018 21:30:43 +0200 Michael Biebl <[email protected]> wrote:
> Am 05.10.18 um 21:28 schrieb Michael Biebl:
> > That said, also keep in mind, that the inhibit mechanism does not work
> > if the reboot request is triggered by privileged users [1], e.g. if you
> > trigger a reboot as root, an existing inhibitor blocks are ignored.
> > [1] https://github.com/systemd/systemd/issues/6644
>
> This issue describes this even better
> https://github.com/systemd/systemd/issues/2680
It seems there is no real interest to change this upstream and even if
at some point in the future there was a way to make inhibitors work for
the root user, I think such an inhibitor lock shoud be take directly by
dpkg. I don't think the hook interface is sufficient for that.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
