pcp
[Top] [All Lists]

[Bug 1225599] New: default-on for pmcd/etc. under new fedora packaging g

To: pcp@xxxxxxxxxxx
Subject: [Bug 1225599] New: default-on for pmcd/etc. under new fedora packaging guidelines
From: bugzilla@xxxxxxxxxx
Date: Wed, 27 May 2015 18:37:07 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
https://bugzilla.redhat.com/show_bug.cgi?id=1225599

            Bug ID: 1225599
           Summary: default-on for pmcd/etc. under new fedora packaging
                    guidelines
           Product: Fedora
           Version: rawhide
         Component: pcp
          Assignee: nathans@xxxxxxxxxx
          Reporter: fche@xxxxxxxxxx
        QA Contact: extras-qa@xxxxxxxxxxxxxxxxx
                CC: brolley@xxxxxxxxxx, fche@xxxxxxxxxx, lberk@xxxxxxxxxx,
                    mgoodwin@xxxxxxxxxx, nathans@xxxxxxxxxx,
                    pcp@xxxxxxxxxxx, scox@xxxxxxxxxx



As per https://fedorahosted.org/fesco/ticket/1446 and
https://fedoraproject.org/wiki/Packaging:DefaultServices etc., future fedoras
will permit services to be on-by-default as long as they don't bind to external
network interfaces.  So, if our pmcd etc. services grew an option to bind only
to localhost / AF_UNIX, and those options were set in/via the .service files,
those services could be added to the distro's systemd-presets file.

The fedora policy guidelines unfortunately don't note a preferred method for
opening up the services for network access, should a sysadmin later want
cross-network capabilities.  Instead of hand-editing a .service file, maybe an
EnvironmentFile=-/etc/sysconfig/pcp-network-p driven common option flag?  Maybe
packaged in another pcp-network-enable subrpm that also opens up the system
firewall upon installation?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=RaJu2s7StT&a=cc_unsubscribe

<Prev in Thread] Current Thread [Next in Thread>