linux/poky.git/meta/classes/systemd.bbclass, branch yocto-2.2.2

systemd.bbclass: don't block on service restart

2017-01-11T17:21:43+00:00

The current class works fine when a recipe uses SYSTEMD_AUTO_ENABLE 'enable' and has no on device pkg_postinst(), ie when the postinst is run as part of rootfs creation. However, when there is a component of pkg_postinst() that is run on device the 'systemctl restart' is run as part of the run_postinsts.service at boot. This results in the boot spinning indefinitely with: [ *** ] A start job is running for Run pending postinsts (7s / no limit) The issue could potentially be that the packages service has an 'After' clause which comes later in the boot, beyond run_postinsts.service, creating a chicken before the egg scenario. Even service files without an 'After' clause cause this situation however. Despite this not being the cause of the issue this fix will prevent this scenario from happenning. Using strace we are able to find that during boot, when run_postinsts.service is running attempting to start or restart any service will result in the call get stuck on poll(). Since the run_postinsts.service does not monitor the outcome of the call to restart we can work around this by using '--no-block'. (From OE-Core rev: 6ad6a0084a73088fc2a27ab9958e5c46d6e094fc) (From OE-Core rev: caad8aa89f9815a278e39296497596996a35fe95) Signed-off-by: Mark Asselstine Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

systemd.bbclass: Use bb.fatal() instead of raising FuncFailed

2016-10-04T15:29:04+00:00

This sets a good example and avoids unnecessarily contributing to perceived complexity and cargo culting. Motivating quote below: < kergoth> the *original* intent was for the function/task to error via whatever appropriate means, bb.fatal, whatever, and funcfailed was what you'd catch if you were calling exec_func/exec_task. that is, it's what those functions raise, not what metadata functions should be raising < kergoth> it didn't end up being used that way < kergoth> but there's really never a reason to raise it yourself FuncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. (From OE-Core rev: 8e956d66087b9c41591b8e4e817ed6c9e42f5981) Signed-off-by: Ulf Magnusson Signed-off-by: Richard Purdie

systemd.bbclass: Allow enabling of parameterised services

2015-12-09T08:48:24+00:00

Currently the systemd.class will check whether a service exists when it is requested to enabled it. However, its check does not take into account that a service like 'foo@eth0.service' can be enabled from a service named 'foo@.service'. This patch alters the check function in systemd.class to look for 'foo@.service' if the normal check fails. (From OE-Core rev: 4ce15271dad3520e5de2500c609b05d5a511e453) Signed-off-by: Bob Ham Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemd.bbclass: Use systemd_system_unitdir

2015-08-10T19:40:29+00:00

(From OE-Core rev: 0cd61456c0ae912b9fa525db1b3c811e01349d27) Signed-off-by: Pau Espin Pedrol Signed-off-by: Richard Purdie

systemd.bbclass: drop has_exactly_one_service setting

2015-05-14T10:44:00+00:00

The has_exactly_one_service variable was used in now deleted code. Drop this part to make code cleaner. (From OE-Core rev: 8acee5a86efd146186e0de1c41d0e4e4223d8b36) Signed-off-by: Dmitry Eremin-Solenikov Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemd: don't add files and dependencies from units Conflicts

2014-11-04T10:27:11+00:00

Adding dependencies and moving files based on Conflicts tags in unit files isn't right, mainly as it means that systemd depends on systemd-binfmt, because the latter ends up containing the shutdown.target unit. (From OE-Core rev: 02767aac492cedf6ccd02648b8e65751cc23c11c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

update-rc.d/systemd: Remove OVERRIDES dependency

2014-09-23T20:38:59+00:00

Taking run-postinsts and building for two machines which have different OVERRIDES leads to two different sets of stamps for an allarch package. We don't need to depend on OVERRIDES in these classes, the end resulting variables are good enough. We can therefore exclude the dependency and allow a single package to be generated for run-postinsts. (From OE-Core rev: fdc949154e64afb41dd4db3a97be74a15963128d) Signed-off-by: Richard Purdie

Globally replace oe.utils.contains to bb.utils.contains

2014-04-25T16:19:19+00:00

BitBake has the exact same code as oe.utils.contains so there's no reason to duplicate it. We now rely on the bb.utils.contains code for metadata. (From OE-Core rev: 93499ebc46547f5bf6dcecd5a786ead9f726de28) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

systemd: pass --root in prerm if running on host

2013-12-18T17:08:06+00:00

If a systemd image is built without a package manager then packages will be removed from an image during rootfs generation, but without passing --root the systemctl will look on the *host* system. (From OE-Core rev: d01da862d10d9544f8da846b577cf955041d4c0c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes/recipes: More optimal DISTRO_FEATURES references

2013-12-05T14:24:43+00:00

Using the contains function results in more optimal sstate checksums resulting in better cache reuse as we as more consistent code. (From OE-Core rev: 9c93526756e7cbbff027c88eb972f877bcb1f057) Signed-off-by: Richard Purdie