A stop job is running for Builds?

[Reindl Harald]

Am 22.07.2016 um 13:31 schrieb Tom Horsley:
> I just did a dnf update on my f24 desktop. I saw new nvidia akmod
> source get loaded from rpmfusion. After dnf finished the update, I watched
> a bunch of c compiles, depmods, etc. being run by akmod.
>
> After that all finished, I rebooted the system, and on the way
> down, systemd got hung counting up to 1m 30s saying that
> a stop job was running for Builds of akmods.
>
> It looks like systemd wasn't aware that the build had already
> finished. Is this an akmod bug of some kind?
>
> Anyone know what systemd is looking at to make it wait on this?
> I could add it to my script full of all sorts of things I manually
> bash over the head to make systemd not wait on them :-). (Which
> I run as part of my "reboot" alias)

that is a well known repeatly arriving problem

here you go:
https://www.google.com/search?q=systemd+a+stop+job+is+running

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.rpmfusion.org/pipermail/rpmfusion-users/attachments/20160722/43e03904/attachment.sig>