Re: [systemd-devel] Question about system-update.target

[AbH Belxjander Draconis Serechai]

This seems to putthe requirement of an If(a||b||c)==Failure Then
reboot.target

Where a b and c are ALL required to complete before rebooting occurs.

I would thing to specifically handle each tool as a process,

Would a specific script or tool already be available?

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?

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.

Hopefully I am understanding the issue with a possible execution strategy
for this specific case?

Is it even practical with current tools in some way?
On 27/04/2015 5:52 PM, Richard Hughes hughsi...@gmail.com wrote:

 At the moment the only user of system-update.target is PackageKit,
 which does package updates offline in the special system-update boot
 target. The other project that has just started using this mode is
 fwupd, which is using it to update BIOS-based firmware (not UEFI
 capsules) offline.

 I've installed a symlink to system-update.target.wants so that the
 fwupd process gets run, but I'm a little worried about what happens
 when there are two optional services being run, both with
 OnFailure=reboot.target

 What return code I supposed to return if we launch
 fwupd-offline-update.service and there are no BIOS updates to apply?
 It seems to me that we want the behaviour of OnFailure to be if
 none of the *-offline-update.service files returned success rather
 than what happens now in that we launch pk-offline-update with no
 package updates which returns failure, which reboots the machine
 before the fwupd offline update process even gets a chance to properly
 start.

 Ideas welcome, thanks.

 Richard
 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] simultaneous udp listeners for ipv4+6 caused systemd to go into a loop

[AbH Belxjander Draconis Serechai]

It is asking for the same resource twice in the way I read that

aren't IPv4 and IPv6 sharing socket space?
that would be a resource allocation error if true right?
On Dec 5, 2012 8:53 AM, Mirco Tischler mt...@gmx.de wrote:

 2012/12/5 Thomas H.P. Andersen pho...@gmail.com

 I was looking into why the unit files for talkd/ntalkd were not
 working [1]. For some reason specifying these two lines in the same
 socket file triggers an unfortunate behavior in systemd:
 ListenDatagram=[::]:517
 ListenDatagram=0.0.0.0:517

 Systemd first of all fails to start the service. It then tries
 starting it again and again repeatedly. This quickly reaches the limit
 for failing to start a service too often. It still just continues and
 it spams the journal about having hit this limit. It caused a
 noticeable slow down of the computer and my log file began rotating.

 I have not looked into what is going on in systemd, or whether this is
 a bug or not. However it is case where I think that it could be nice
 to provide a clear error message.

 Maybe someone can spread some light about what is going on here? A
 socket file with just one of the two ListenDatagram-lines works just
 fine.

 [1] https://bugzilla.redhat.com/show_bug.cgi?id=737219


 My guess is systemd gets confused because the two addresses overlap. By
 default specifying an ipv6 address will make the service available on both
 ipv6 and ipv4, so the second directive is redundant. This can be disabled
 with BindIPv6Only=ipv6-only. But systemd could indeed behave nicer in this
 situation :)

 Mirco

 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel