On 12/02/2019 19:20, Ludwig Nussel wrote:
Thorsten Kukuk schrieb:
On Mon, Feb 11, Patrick Shanahan wrote:
* Matwey V. Kornilov
[02-11-19 07:24]: What is the recommended way to start the socket unit just after installation?
I see that cups.socket is also inactive just after cups installation, but erlang really relies on epmd.socket running.
there really are man pages and examples systemctl start <particular service> systemctl start cups
This is something you can do on the commandline, but never! from a pre/post script. And I think this is what Matwey was asking for: if the package get's installed, it should start automatically. We never do that for security and stability reasons.
Unless it's a dbus service. When set up correctly a dbus services will autolaunch just fine right after installation as soon as some program asks for it on the bus. If that is ok I actually don't see a reason to not allow the same for sockets. It's just that AFAIK infrastructure is not in place to do that properly. Clearly explicit "systemctl start" lines in %post woulnd't be the right way. We'd have to extend the presets mechanism so activating sockets happens transparently and package(r)s don't have to worry.
cu Ludwig
Once we get to the point of discussing changes like this we probably should be doing it on the factory list because there's a number of people interested in the discussion that are not on this list. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B