On Sun, Feb 10, 2019 at 4:40 AM Georg Sauthoff <mail@xxxxxxxx> wrote:
>
> Hello,
>
> 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.
>
> > The new dstat script resides in the pcp-system-tools sub-package of
> > PCP. This package depends on python3, python3-pcp and pcp-libs. None
> > of these packages contain systemd services.
>
> The {pmcd,pmlogger,pmie}.service files are provided by the 'pcp'
> package. And pcp-system-tools *does* depend on pcp. See also:
>
> # dnf remove pcp
> Dependencies resolved.
> ================================================================================
> Package Arch Version Repository Size
> ================================================================================
> Removing:
> pcp x86_64 4.3.0-3.fc29 @updates 4.2 M
> Removing dependent packages:
> pcp-system-tools x86_64 4.3.0-3.fc29 @updates 620 k
>
>
> [..]
> > I wonder if you have installed the (optional) pcp-zeroconf package,
> > Georg? This is a convenience package which automates setup of
>
> No, I don't have it installed:
>
> # rpm -q pcp-zeroconf
> package pcp-zeroconf is not installed
>
> > frequently needed PCP services for use in customer support situations.
> > You do not need to install this package to use dstat.
>
> As-is, because of the dependencies (see above) I have to install them.
>
> > The new dstat does not require running services, by default it runs in
>
> Yes, this is true, the service don't need to be running for the new dstat.
>
> > a standalone fashion.
> [..]
>
> > > Perhaps it's just me, but having 3 services enabled after installing the
> > > dstat replacement ('which strives for 100% output compatibility with the
> > > original dstat') feels like a violation of the principle of least
> > > astonishment.
>
> > Agreed - that's why the code is written the way it is, and the
> > packages are structured the way they are. It is not the case that you
> > need to have 3 additional services running when using the new dstat.
>
> The problem is that pmie/pmcd/pmlogger are enabled by default because they have
> their 'vendor preset' configured to 'enabled'. See also:
>
> # systemctl status pmie pmcd pmlogger
> ● pmie.service - Performance Metrics Inference Engine
> Loaded: loaded (/usr/lib/systemd/system/pmie.service; disabled; vendor preset: enabled)
> [..]
>
> # find /usr/lib/systemd -name '*.preset' | xargs grep '\<\(pmcd\|pmlogger\|pmie\)'
> /usr/lib/systemd/system-preset/90-default.preset:enable pmcd.service
> /usr/lib/systemd/system-preset/90-default.preset:enable pmlogger.service
> /usr/lib/systemd/system-preset/90-default.preset:enable pmie.service
>
> # dnf provides /usr/lib/systemd/system-preset/90-default.preset
> fedora-release-29-7.noarch : Fedora release files
> [..]
>
> Do I need to create a Bugzilla tickets for fixing the pcp dependencies and
> presets or do you take care of it?
>
> Best regards
> Georg
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.
_______________________________________________
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
