Date: Sun, 15 Oct 2017 23:01:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 223038] Update mail/opendkim: Fix rc script chmod Message-ID: <bug-223038-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223038 Bug ID: 223038 Summary: Update mail/opendkim: Fix rc script chmod Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: douglas@douglasthrift.net CC: freebsd-ports@dan.me.uk Attachment #187204 maintainer-approval?(freebsd-ports@dan.me.uk) Flags: CC: freebsd-ports@dan.me.uk Flags: maintainer-feedback?(freebsd-ports@dan.me.uk) Created attachment 187204 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187204&action= =3Dedit mail/opendkim-2.10.3_8.diff The comments in the milter-opendkim rc script state that milteropendkim_soc= ket is one of the parameters that can instead be set in opendkim.conf(5) config file. However, when running the rc script to start or restart the daemon, t= he usage for chmod is printed as if it was invoked with incorrect parameters. I tracked this down to milteropendkim_socket being unset and [ -S ... ] retur= ning 0 in sh if its argument is blank and unquoted in the dkim_start_postcmd function. I have provided a patch which avoids this by first checking if milteropendkim_socket is not blank. portlint: OK (0 fatal errors and 16 warnings found.) testport: OK (poudriere: 103i386, 103amd64, 111i386, 111amd64) --=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-223038-13>