summaryrefslogtreecommitdiffstats
path: root/meta/classes/kernel-uboot.bbclass
diff options
context:
space:
mode:
authorBedel, Alban <alban.bedel@aerq.com>2019-07-23 14:11:46 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-07-26 08:41:38 +0100
commit3ac4332d2565c04e9be936d2397453f7041003b1 (patch)
treef53ddf5bc9a893e36530d57b3367cfaf603563e8 /meta/classes/kernel-uboot.bbclass
parentd3ed42ef277c0d82928fa7ea95597e46e22a93c2 (diff)
downloadpoky-3ac4332d2565c04e9be936d2397453f7041003b1.tar.gz
rng-tools: start rngd early in the boot process again
It do make sense to start rngd early in the boot process because otherwise we would need to track every service that might need entropy and explicitly configure it to start after rngd. When used with systemd rngd blocked the shutdown process because it simply missed the proper unit configuration. As the systemd documentation explains, when using DefaultDependencies=no one also have to explicitly configure the unit to properly stop at some point. This is normaly achieved by having Before=shutdown.target and Conflicts=shutdown.target set for the unit. To have rngd started early again we reverte the changes done to rngd.service in commit edf7606822 (rng-tools: fix rngd blocks system shutdown). To have it properly stopped on shutdown we also add Before=shutdown.target and Conflicts=shutdown.target. (From OE-Core rev: a74e7df33e2c8ab2152e3217c0a5df3f65971713) Signed-off-by: Alban Bedel <alban.bedel@aerq.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/kernel-uboot.bbclass')
0 files changed, 0 insertions, 0 deletions