Ah, to clarify, I'm talking about app-specific servers not Linux
system services, so dbus isn't really relevant (what would it be used
for?). The sort of programs that tend to be packaged with Docker
today, or deployed using AWS Lambda or just copied up to the server.
For example a typical
Sorry, by "apps" I meant anything not supplied by OS developers. In
this context, servers e.g. custom web app servers. I do currently run
some of those with DynamicUser=1 and similar.
> As long as the tool updating the disk image creates the new one under
> a temporary name, and then replaces the
> There's currently no mechanism for that. File an RFE issue.
https://github.com/systemd/systemd/issues/26647
> In the "Portable Services" concept we currently assume you update the
> disk image ("DDI") the service is on, and then simply restart the
> service while leaving the socket around.
I see. So basically you have to keep the service running across the upgrade
and then wait for it to shut down due to inactivity, then be restarted by
systemd to make the update apply. Or alternatively you could make the app
detect that it's been updated, stop accepting new connections, finish
Hi,
I'm exploring socket activation as part of work on a tool that makes
systemd-controlled servers easier to deploy and use. Given a config
file the tool builds a package that contains the app and systemd
units, uploads it, installs it with dependency resolution, the
postinst scripts start the
