Date: Tue, 30 Aug 2016 16:31:13 -0500 From: Doug McIntyre <merlyn@geeks.org> To: freebsd-questions@freebsd.org Subject: Recent changes to Apache 2.4's SUEXEC path? Message-ID: <20160830213113.GA31117@geeks.org>
next in thread | raw e-mail | index | archive | help
I've been trying to track down a change to Apache 2.4's SUEXEC path, and I just don't where where or when things may have done it. Background, I've got a Pouderier server for doing my site-wide builds. At one point, with no Apache options set for my builds, the SUEXEC_BIN path was set to what I was expecting. /usr/local/sbin/suexec Ie. from a machine that installs packages from my local builder.. $ strings /usr/local/sbin/httpd | fgrep SUEXEC -D SUEXEC_BIN="/usr/local/sbin/suexec" However, after time I started building more packages, and I see that in the packages downloaded directly from pkg.FreeBSD.org, I get this instead.. pkg:~> strings /usr/local/sbin/httpd | fgrep SUEXEC -D SUEXEC_BIN="/usr/local/bin/suexec" And now port builds on my Pouderier building have a different SUEXEC_BIN between Apache and the other mods I've built. I can't find where the SUEXEC_BIN path is set in the port at all, I find no mention in the port Makefile, or any port patches specific to Apache. I don't find any history or changelog for anything like this change. :-( Does anybody have any information or history on what might have changed where? I assume I'll have to do a force rebuild of all packages on my pouderier builder system now to get everything to match again?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160830213113.GA31117>