A stop job is running for Builds?

[Ed Greshko]

On 07/22/16 19:31, Tom Horsley wrote:
> 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).

FWIW, I always check /var/cache/akmods/akmods.log to make sure everything is *really*
finished.  I've had times where there was a considerable gap between the time the builds
of the kmods was done and when dnf itself was finished installing them.