> 1. does on the system running also take quite some time if you do like
"systemctl stop irqbalance"?
I have tested this now multiple times by stopping and starting it again
and all looked fine.
> 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.
Based on the above this might be true. So is it a known issue that
systemd prints wrong things? I think this is an issue that should be
actually fixed before tinkering around on every shutdow delay issue
(also [1] blames that [2] isn't reliable enough so it would eventually
also make sense to wait for [1]'s implementation).
** Changed in: irqbalance (Ubuntu)
Status: Incomplete => New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1729192
Title:
Shutdown needs often longer than usual
Status in irqbalance package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
I'm using Ubuntu 18.04 dev with irqbalance 1.1.0-2.3ubuntu1 and for
some weeks on shutting down the system often (around 50%-75%) I'm
seeing that the irqbalance job needs some seconds to shutdown causing
to delay the system shutdown noticeable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1729192/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
