© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi,
I doubt it is irqbalance shutdown in your case.
That shutdown is just sending a kill signal and that is it, there is not much more it does.
I quickly checked but for me it didn't look the same.
Two things to get more details:
1. does on the system running also take quite some time if you do like "systemctl stop irqbalance"?
2. I'd assume that systemd concurrently stops multiple things and irqbalance is just the last to print but not the one you are actually waiting on. To check that unfortunately [1] isn't implemented - but you can check if [2] gives you some hints what it is actually waiting on.
[1]: https:/
[2]: https:/