[Bug 262473] mail/opendkim: inconsistent PID handling in rc
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262473] mail/opendkim: inconsistent PID handling in rc"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262473] mail/opendkim: inconsistent PID handling in rc"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262473] mail/opendkim: inconsistent PID handling in rc"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262473] mail/opendkim: inconsistent PID handling in rc"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 10 Mar 2022 18:26:26 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262473
Bug ID: 262473
Summary: mail/opendkim: inconsistent PID handling in rc
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: contact@evilham.com
CC: freebsd-ports@dan.me.uk
CC: freebsd-ports@dan.me.uk
Flags: maintainer-feedback?(freebsd-ports@dan.me.uk)
I found a couple issues with the port that *might* be related to #258011 and
certainly are related to #254762.
Out of the box (after installing opendkim), the port behaves in a strange
fashion when not using profiles.
After some debugging, I came to realise that this is due to the rc script
setting the PID file to:
/var/run/milteropendkim/pid, where /var/run/milteropendkim is not created.
Therefore `service milter-opendkim start` results in the process starting, but
status / restart / stop being useless (due to the PID not being created).
This is the first issue.
The second issue resulted when trying to force in the config:
PidFile /var/run/opendkim.pid
Which does not work as the rc script is lacking "dkim_get_pidfile" in the
branch that handles a call without arguments and without profiles enabled.
As a work-around, running mkdir /var/run/milteropendkim means that the service
works, but these two issues exist in the port and should be solved.
--
You are receiving this mail because:
You are the assignee for the bug.