Wanted to ask about a minor nitpick I’ve had recently after installing Fedora w/ KDE to my Thinkpad L14, G1 AMD, via the “Everything” netinstall ISO.
Whether shutting down from the respective application launcher button, or Konsole with the including the --no-wall option, I get this broadcast message.
It’s an odd hang in what I’ve otherwise configured to be a seamless experience in using Fedora. I haven’t had this occur on my desktop with a similar set-up using KDE, other desktop environments seem to be free of this issue when testing on my Thinkpad too, so I’m stumped.
Not really what I’m looking for… shutdown --no-wall seems to work after running systemctl halt --no-wall, but it’s still not the solution I’m looking for.
I’d like for the --no-wall option to be the default system-wide, or at least what KDE’s power button will default to.
FYI This is a alias for the systemctl commands to reboot/shutdown etc.
These run services to do the shutdown - maybe an edit to the service can stop the wall.
The other option would be to use mesg n in the terminals.
I haven’t had to poke around with configuring services before, so I’m a bit lost as to where to begin.
mesg n didn’t do much for it.
I tried copying logind.conf from /usr/lib/systemd/ to /etc/systemd/, appending WallMessages=no at the end and running systemctl reload systemd-logind to (hopefully) apply the changes, still getting the shutdown broadcast.
On the contrary. mesg has only effect in the current terminal and must be repeated everytime you open up another terminal. On reboot, everything reverts back to default.
You can see the effect when running ls -l /dev/pts/* where the group permission is set to “-w-” to allow the messages to be written to the tty device. The tty command will display the exact name of that tty device, and all open terminals get individual tty device names attached.
You can’t block user root’s messages. These are important, it could be emergency/critical warnings issued by the kernel. Why would you want to block such messages?
