Your message dated Wed, 18 Jul 2018 16:38:21 +0200
with message-id <[email protected]>
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 [email protected]
immediately.)
--
810608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810608
Debian Bug Tracking System
Contact [email protected] 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 ---
> Yes, I confirm that issuing
>
> $ su -
> Password:
> # shutdown 5
> Shutdown scheduled for Sun 2016-01-10 18:54:54 CET, use 'shutdown -c' to
> cancel.
> # Connection to HOSTNAME closed by remote host.
> Connection to HOSTNAME closed.
>
> or
>
> $ su -
> Password:
> # shutdown
> Shutdown scheduled for Sun 2016-01-10 19:02:32 CET, use 'shutdown -c' to
> cancel.
> # exit
> $ echo 'I am a regular user now'
> I am a regular user now
> $ Connection to HOSTNAME closed by remote host.
> Connection to HOSTNAME closed.
>
> failed to show the broadcast message to the users.
I tested this on a stable system, for a locally logged in user and one
logged in via SSH.
Both got the wall message
Broadcast message from root@debian on tty1 (Wed 2018-07-18 16:37:14 CEST):
The system is going down for poweroff at Wed 2018-07-18 16:38:14 CEST!
I thus conclude that this issue has been fixed in the mean time and will
close the bug accordingly.
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 ---
