[Bug 199995] sysutils/puppet -- the 'Service' provider will get service names wrong when rc scripts contain a 'desc' parameter

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199995

            Bug ID: 199995
           Summary: sysutils/puppet -- the 'Service' provider will get
                    service names wrong when rc scripts contain a 'desc'
                    parameter
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: swills at FreeBSD.org
          Reporter: matthew at FreeBSD.org
             Flags: maintainer-feedback?(swills at FreeBSD.org)
          Assignee: swills at FreeBSD.org

Created attachment 156427
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=156427&action=edit
Update to sysutils/puppet

puppet groks the 'service_name' parameter by parsing the output of 'service foo
rcvar'.  Normall this works well, but in the case of eg. local_unbound, it goes
comically wrong:
{{{
:% service local_unbound rcvar 
# local_unbound : local caching forwarding resolver
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#
local_unbound_enable="NO"
#   (default: "")

}}}

The indicated text comes from the 'desc' variable in /etc/rc.d/local_unbound,
and leads to puppet creating a file '/etc/rc.conf.d/local_unbound : local
caching forwarding resolver' (embedded spaces and colons and all).  Needless to
say, this doesn't get read-in by the rc-system.  Admittedly, local_unbound is
one of only two rc-scripts in the base system that contain a desc fiels (at
least, in 10.1-RELEASE)

I've submitted a bug upstream, but in the mean time, the attached patch fixes
the problem for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.