Your message dated Tue, 22 Aug 2023 23:35:40 +0200
with message-id <674d22c0-b790-4540-a78b-aae57eeb6...@debian.org>
and subject line Re: Bug#810608: systemd-sysv: on shutdown, fails to inform
users that the system is going down
has caused the Debian Bug report #810608,
regarding systemd-sysv: on shutdown, fails to inform users that the system is
going down
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 ow...@bugs.debian.org
immediately.)
--
810608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 228-2+b1
Severity: normal
Hello,
I noticed a feature that systemd seems to lack.
When the box is being shut down (reboot or halt or poweroff), users
are not notified in any way of what is happening.
For instance, any remote user (connected via SSH) is correctly
forced out of the system (provided that libpam-systemd is installed
and OpenSSH has UsePAM enabled, see bug #751636 for the long
discussion about this), but there is no indication as to why
the user was kicked out.
On boxes that have sysvinit as PID 1, the users get an informative:
Broadcast message from root@HOSTNAME (pts/0) (CURRENT TIME):
The system is going down for reboot NOW!
or
Broadcast message from root@HOSTNAME (pts/0) (CURRENT TIME):
The system is going down for system halt NOW!
Could this feature be implemented in systemd as well?
It should be easy to add an appropriate wall(1) invocation
on shutdown. I hope it can be done soon.
Thanks for your time!
Bye.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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-sysv depends on:
ii systemd 228-2+b1
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 240-1
On Tue, 24 Jul 2018 22:27:05 +0200 Francesco Poli
<invernom...@paranoici.org> wrote:
On Tue, 24 Jul 2018 21:59:56 +0200 Michael Biebl wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/3700
>
> Am 21.07.2018 um 20:07 schrieb Francesco Poli:
> > On Sat, 21 Jul 2018 01:21:52 +0200 Michael Biebl wrote:
> >
> > [...]
> >> For remote logins, it might be useful.
> >
> > Exactly: it is useful to figure out why your SSH connection got closed...
>
> Marking as forwarded
Thank you so much for your prompt and kind reaction! :-)
Now let's hope the bug will be fixed soon...
Supposed to be fixed by
https://github.com/systemd/systemd/commit/3d0ef5c7e00155bc74f6f71c34cad518a4ff56ba
which is part of v240. So closing the bug report accordingly.
Regards,
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
