ostroproject/swupd-daemon

swupd-daemon's Issues

daemon should auto-exit on idle timeout

when idle (ie: no subprocess or clients connected), then the server must gracefully exit to save resources. DBus activation will take care to automatically re-launch it. See what systemd-localed and the likes do.

Ensure that systemd service and dbus services link to each other by means of BusName and SystemdUnitName

Compile time enable/disable for daemon integration in swupd-client

The daemon should be able to be enabled or disabled (with dependencies being required/not required based on that) when integrated with swupd-client.

replace glib with libsystemd

Since this project will be merged in swupd-client, they do not want to depend on glib but are okay with libsystemd, since systemd is a core component of both Ostro and ClearLinux.

The sd-bus.h is very easy to use for both client and server. See an introdution at http://0pointer.de/blog/the-new-sd-bus-api-of-systemd.html and full header at https://github.com/systemd/systemd/blob/master/src/systemd/sd-bus.h

For the main loop concept you can use other parts of libsystemd, like sd-event.h (https://github.com/systemd/systemd/blob/master/src/systemd/sd-event.h)

verify daemon is injection-proof

verify if the line we execute is injection-proof, that is. It may be tricky if we use "system(3)-like" calls, since it could use envvars and $() or ;. It's safer to directly call the binary giving the command array as execve().

(This is more of a reminder, didn't investigate if this is possible with current code)

provide drop-in dbus client as replacement for swupd

since the idea is to replace swupd without breaking user experience, our dbus client should be a drop-in replacement that talks to the actual swupd via the dbus daemon.

This includes progressive delivery of swupd output, so we can get lots and progress on slow downloads and updates.

It is essential to get this merged into swupd-clienti itself, this way clr could use it by default.

TODO: If the client dies, the server may need to cancel the operation? Is it safe?