Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle systemd service file changes / reloads correctly #574

Open
tayzlor opened this issue Jan 4, 2016 · 1 comment
Open

Handle systemd service file changes / reloads correctly #574

tayzlor opened this issue Jan 4, 2016 · 1 comment
Assignees
@enxebre
Labels
bug coreos

Comments

@tayzlor
Copy link
Member

tayzlor commented Jan 4, 2016

At the moment if you change a .service file and try and restart the service you'll receive a warning like -

Warning: marathon.service changed on disk. Run 'systemctl daemon-reload' to reload units.

Running systemctl daemon-reload and then systemctl restart marathon fixes that - we just need to build that into the ansible playbooks
@tayzlor tayzlor changed the title Handle systemd service file changes correctly Handle systemd service file changes / reloads correctly Jan 4, 2016
@tayzlor tayzlor mentioned this issue Jan 4, 2016
Closed
@enxebre
Copy link
Contributor

enxebre commented Jan 8, 2016

we could try to ensure enabled (not started) for every service on tasks and only start them by notifying reload-daemon restart-service

@enxebre enxebre mentioned this issue Jan 11, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@enxebre enxebre

Labels
bug coreos
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@enxebre @tayzlor