-
Notifications
You must be signed in to change notification settings - Fork 72
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.
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
Include socket services while stopping services during restart #653
Conversation
run_service_action('stop', common_options.merge(:include_sockets => true)) | ||
run_service_action('start', common_options) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really wonder why we don't call the restart action. I mean, systemctl
is perfectly capable of calling stop and start itself if there's no restart defined. That also gets rid of the warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mind filing an issue for that? we could ask to include that change here but it sorta muddies the waters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ehelms Could you please create a redmine issue for this? Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two things:
/packit build |
No config file for packit (e.g. For more info, please check out the documentation or contact the Packit team. |
4df23db
to
f790752
Compare
Signed-off-by: Gaurav Talreja <[email protected]>
f790752
to
69b9343
Compare
From my quick test, when we switched to using systemd restart, this was inherently fixed, here is output without this fix:
|
@ehelms Yes, I've also tried, this warning disappears when using restart, but sockets aren't included in it, so do you think if it makes sense to include sockets while restart? if not, then we're good to close this PR I think, Thanks! |
I do not think we need to include sockets as systemd handles this for us. |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2067120
Results: