Bug 1413537

Summary:	usr/bin/shutdown --no-wall argument ignored
Product:	[Fedora] Fedora	Reporter:	Michal Schorm <mschorm>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	25	CC:	johannbg, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-06 10:34:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Schorm 2017-01-16 10:32:53 UTC

When I use "shutdown -r --no-wall", the "--no-wall" argument is ignored.

Spotted in all Fedora versions.

Severity set to  high, since in some cases it can block user from use of "shutdown -r" (Failed to set wall message, ignoring: Connection timed out)



As I remember, it can be solved most of the times, calling this as a root. However, most of the times I really need this command, I can't log in as root. (Either don't know root credentials or "su" command freeze)

Comment 1 Zbigniew Jędrzejewski-Szmek 2017-01-28 02:57:41 UTC

Are you sure that the argument is ignored? I gave this some (light) testing now, and it seems to work just fine. This is with F25, but this code hasn't changed in ages.

Please note that --no-wall has no influence on whether shutdown comunicates with systemd-logind. It just means that systemd-logind will not broadcast the message, but it'll still be stored in systemd-logind, and can be retrieved e.g. using "loginctl show-session -p WallMessage".

I think this is just a misunderstanding.

Comment 2 Michal Schorm 2017-03-06 10:34:45 UTC

Hi,
under a fresh light of other bug reports, this could be caused by damaged systemd.

The issue appears only together with other bugs I reported.

I'll close this bug until I'll found out, what's wrong with my systemd and how to solve it.

Then it either won't appear again or I'll reopen it with new information.