Date: Sun, 02 Jul 2017 14:47:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216799] mail/dcc-dccd: Fixes for changes in FreeBSD 11 /usr/share/mk Message-ID: <bug-216799-13-en2wIpxwMA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216799-13@https.bugs.freebsd.org/bugzilla/> References: <bug-216799-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=3D216799 --- Comment #8 from Vernon Schryver <vjs@rhyolite.com> --- concerning: > This broke DCC for me (dccproc from SpamAssassin) the mail logs show: > > dccproc[61386]: open(/usr/local/dcc/map): Permission denied > dccproc[61386]: lock_open(/usr/local/dcc/whiteclnt.dccx): Permission deni= ed; > file not writeable for locking > > The install sets the ownership of /usr/local/dcc/ and /usr/local/dcc/map= to > root:wheel, setting them to dcc:dcc fixed the problem. > > ids and ids.sample are also root:wheel, but don't appear to create a prob= lem. I suspect that /usr/local/dcc/whiteclnt.dccx is a typeo for whiteclnt.dccw The ids, map, whiteclnt, and whiteclnt.dccw files and the log directories m= ust be owned by the UID specified by DCCUID in the dcc_conf file and the setuid= UID of dccproc, cdcc, and dccsight. If I am reading "DCCUSER?=3Ddcc" and CONFIGURE_ARGS in a recent /usr/ports/dcc-dccd/Makefile correctly, that UID= is "dcc". Does the pkg_list file need to be adjusted? `make install` in homedir should fix the owners of the ids, map, and whitec= lnt files. If you use the proof-of-concept CGI files (almost no one does), the whitecl= nt files must be writable by the GID of CGI processes, perhaps "www". The log directories should be readable by that GID. Running ${DCCHOME}/libexec/updatedcc is my recommendation for updating an existing DCC installation. vjs --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216799-13-en2wIpxwMA>