* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No * Is the service non-persistent (i.e. run once at startup and exit)? No * What is the exact name (or names) of the systemd unit files to be enabled? snapd.session-agent.socket * Is this request for all Fedora deliverables or only for some Editions (list them)? All Fedora deliverables Additional info: I need this preset also backported to F30 and F29 if possible. This new socket service is being introduced in snapd 2.41.
(In reply to Neal Gompa from comment #0) > > * Is the service non-persistent (i.e. run once at startup and exit)? > > No > This question is a little confusing for a socket-activated service... It runs only for the duration of socket activation and then shuts down, similarly to other session services... Hopefully that makes it clearer?
(In reply to Neal Gompa from comment #1) > (In reply to Neal Gompa from comment #0) > > > > * Is the service non-persistent (i.e. run once at startup and exit)? > > > > No > > > > This question is a little confusing for a socket-activated service... > > It runs only for the duration of socket activation and then shuts down, > similarly to other session services... > > Hopefully that makes it clearer? Right, the purpose of that question was more about "does it establish some configuration and then never run again". A socket-activated service is effectively a persistent service that just happens to have zero footprint most of the time.
https://src.fedoraproject.org/rpms/fedora-release/pull-request/88 (Rawhide) https://src.fedoraproject.org/rpms/fedora-release/pull-request/89 (F30) https://src.fedoraproject.org/rpms/fedora-release/pull-request/90 (F29)
Gave individual thumbs up in the PRs, but covering my base here by saying they all look good to me. :)
PRs are merged. They will be included the next time Mohan does a build of fedora-release.
FEDORA-2019-05873268e5 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-05873268e5
FEDORA-2019-b52f7b7cea has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b52f7b7cea
fedora-release-30-5 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-05873268e5
fedora-release-29-11 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b52f7b7cea
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
fedora-release-29-11 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
fedora-release-30-5 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Built