On Mon, Feb 11, 2019 at 07:53:57AM -0500, Stephen Gallagher wrote: > On Sun, Feb 10, 2019 at 4:40 AM Georg Sauthoff <mail@xxxxxxxx> wrote: > > On Sun, Feb 10, 2019 at 10:08:51AM +1100, Nathan Scott wrote: > > > On Sun, Feb 10, 2019 at 6:47 AM Georg Sauthoff <mail@xxxxxxxx> wrote: > > > > [...] > > > > I'm asking because installing the dstat replacement[1] in Fedora 29 > > > > resulted in 3 additional always running systemd services[2] and 2 open > > > > ports. [..] > For the record, a Bugzilla ticket was filed when these were originally > added (and if you looked at 90-default.preset instead of just grepping > it, you'd notice that it was in a comment immediately above those > enablements). > > The BZ is https://bugzilla.redhat.com/show_bug.cgi?id=1472350 and > included the following text when it was filed: > > """ > > * Does the service listen on a network socket for connections > originating on a separate physical or virtual machine? > Both pmcd and pmlogger can be configured to do so. However, for the > purpose of this bugzilla and being enabled upon install, the default > will be configured for with no listening on network sockets > (adjustable later by the end-user if desired). > > """ > > Because the default configuration did not (at the time) open any > network sockets for listening, it was approved without FESCo > exception, because it was within the guidelines from > https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/#_enabling_services_by_default > If you are asserting that it now *does* listen on those sockets by > default, that's a problem and we need to open a FESCo ticket. Yes, I'm asserting this and I already asserted it in my original mail. See also: # ss -lntp | grep 'pmlogger\|pmcd' | column -t LISTEN 0 5 0.0.0.0:4330 0.0.0.0:* users:(("pmlogger",pid=6353,fd=9)) LISTEN 0 5 0.0.0.0:44321 0.0.0.0:* users:(("pmcd",pid=1135,fd=0)) LISTEN 0 5 [::]:4330 [::]:* users:(("pmlogger",pid=6353,fd=10)) LISTEN 0 5 [::]:44321 [::]:* users:(("pmcd",pid=1135,fd=3)) And yes, all I did on that machine regarding pcp was to execute a `dnf install pcp-system-tools` to get the `dstat` command. There are basically 2 issues: 1) The dependencies of the package that provides the dstat replacement (i.e. pcp-system-tools) 2) The vendor presets of the pmlogger/pmcd/pmie services (which are currently provided by pcp) Perhaps we can agree to fix the current state to this user experience: -- User wants to use dstat => User learns that the original dstat was replaced by the pcp tool of the same name => User installs the pcp package that provides the dstat replacement (e.g. pcp-system-tools) => User can successfully use the `dstat` command which behaves as the old dstat command => No additional services are running => No additional ports are open There are different ways to improve the user experience in that way: a) Fix the dependencies of pcp-system-tools such that it doesn't require the pcp package (which provides the pmcd/pmlogger/pmie services), and/or b) Change the vendor presets for the pmcd/pmlogger/pmie services to disabled, or c) Change the packaging in some other way Best regards Georg _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
