Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Jul 2017 16:01:28 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 123411] [PATCH] mail/postfix-policyd-weight - rc.d startup script does not correctly show status because "name" is set incorrectly.
Message-ID:  <bug-123411-13-5S73JbIvA9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-123411-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-123411-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D123411

Dan McGrath <danmcgrath.ca@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |danmcgrath.ca@gmail.com

--- Comment #7 from Dan McGrath <danmcgrath.ca@gmail.com> ---
Hi,

I think this bug is still a problem, at least in 2017Q3 branch that I am us=
ing.
Namely it breaks the saltstack "enable" service due to the way it does the
lookup and checks the name and compares to the rc.d script name.

I am not exactly who is at fault here as it might be more of a problem with
salt and the logic is uses. In the end, I use a state with:

mail/postfix-policyd-weight:
  pkg:
    - installed
  service:
    - name: policyd-weight
    - running
    - enable: True

Salt is able to start this service, but it never modifies the rc.conf and it
doesn't understand the convention used, thus it would fail a restart of the
host/jail this state is applied to unless a salt highstate is run to correct
the issue.

While I can work around this with salt by manually editing the rc.conf, I
wonder if this bug needs to be revisited?

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-123411-13-5S73JbIvA9>