<p dir="ltr">This seems to putthe requirement of an If(a||b||c)==Failure Then reboot.target</p>
<p dir="ltr">Where a b and c are ALL required to complete before rebooting occurs.</p>
<p dir="ltr">I would thing to specifically handle each tool as a process,</p>
<p dir="ltr">Would a specific script or tool already be available?</p>
<p dir="ltr">Is it possible to one-shot async run given services using systemctl then afterwards pull status and log the individual failure before restarting as a desired behavior here?</p>
<p dir="ltr">Personally I would make a custom service as the update target and specifically have it failover to reboot once ALL depends have been run as one-shot fire-until-finished-with-exit strategy.</p>
<p dir="ltr">Hopefully I am understanding the issue with a possible execution strategy for this specific case?</p>
<p dir="ltr">Is it even practical with current tools in some way?</p>
<div class="gmail_quote">On 27/04/2015 5:52 PM, "Richard Hughes" <<a href="mailto:hughsient@gmail.com">hughsient@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">At the moment the only user of system-update.target is PackageKit,<br>
which does package updates offline in the special system-update boot<br>
target. The other project that has just started using this mode is<br>
fwupd, which is using it to update BIOS-based firmware (not UEFI<br>
capsules) offline.<br>
<br>
I've installed a symlink to system-update.target.wants so that the<br>
fwupd process gets run, but I'm a little worried about what happens<br>
when there are two optional services being run, both with<br>
OnFailure=reboot.target<br>
<br>
What return code I supposed to return if we launch<br>
fwupd-offline-update.service and there are no BIOS updates to apply?<br>
It seems to me that we want the behaviour of "OnFailure" to be "if<br>
none of the *-offline-update.service files returned success" rather<br>
than what happens now in that we launch pk-offline-update with no<br>
package updates which returns failure, which reboots the machine<br>
before the fwupd offline update process even gets a chance to properly<br>
start.<br>
<br>
Ideas welcome, thanks.<br>
<br>
Richard<br>
_______________________________________________<br>
systemd-devel mailing list<br>
<a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br>
</blockquote></div>