4 ms·
The problem here, though, is that they're requesting programs which used to be able to persist via call foo() to call bar() instead if they want to persist on l
by rincebrain 10y ago
The problem here, though, is that they're requesting programs which used to be able to persist via call foo() to call bar() instead if they want to persist on logout, only on Linux.
As someone in the linked issue remarked, this will end with everyone calling bar() if they want to persist (the same way they already called foo()), and we'll still have the same level of persistent process issues, but with a systemd dependency.
- themartorana 10y agoBest explanation of the core issue thus far.
- Spivak 10y ago> but with a systemd dependency. Worse, this isn't "the systemd developers have proposed a new common API for simplified persistent processes across platforms", but a hard dependency on this particular revision of the systemd dbus interface, or using the systemd-run application to generate a user service file.