Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • R rbfsmi-ansible
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • rbfsmi.imt
  • rbfsmi-ansible
  • Issues
  • #6
Closed
Open
Issue created Oct 29, 2020 by Alex Wiens@awiens

`systemctl daemon-reload` at the end of ansible-pull?

If ansible-pull changes systemd unit files systemd will not pick up the changes.

systemctl daemon-reload would be necessary to let systemd load all the changes immediately after ansible-pull is done.

Is it a good idea to add systemctl daemon-reload as ExecStopPost to ansible-pull.service?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking