Skip to content

fix: correct handler name for systemd daemon reload#94

Open
aaronk1 wants to merge 1 commit intoansible-lockdown:develfrom
aaronk1:fix/handler-systemd-daemon-reload
Open

fix: correct handler name for systemd daemon reload#94
aaronk1 wants to merge 1 commit intoansible-lockdown:develfrom
aaronk1:fix/handler-systemd-daemon-reload

Conversation

@aaronk1
Copy link
Copy Markdown

@aaronk1 aaronk1 commented Apr 18, 2026

Summary

The handler name Systemd_daemon_reload uses an underscore which does not match the notify references in tasks that call Systemd daemon reload (with a space). This causes the handler to never fire.

Fix: rename the handler to Systemd daemon reload to match all notify references.

Signed-off-by: aaronk1 aaronk1@users.noreply.github.com

Rule 3.1.3 notified 'Systemd_daemon_reload' (underscore) but the
handler in handlers/main.yml is named 'Systemd daemon reload' (spaces).
Ansible does exact string matching on handler names, so the handler
silently never fired after masking bluetooth.service.

Same pattern as the postfix handler fix in ansible-lockdown#47.

Signed-off-by: Aaron Klepinger <aaronk1@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

Congrats on opening your first pull request and thank you for taking the time to help improve Ansible-Lockdown!
Please join in the conversation happening on the Discord Server as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant