Date: Sun, 26 Jun 2016 08:48:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 210584] lang/php70 - Prevent creation of default www.conf pool Message-ID: <bug-210584-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210584 Bug ID: 210584 Summary: lang/php70 - Prevent creation of default www.conf pool Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: miwi@FreeBSD.org Reporter: purpleritza@gmail.com Assignee: miwi@FreeBSD.org Flags: maintainer-feedback?(miwi@FreeBSD.org) Any chance of disabling creation of www.conf pool each time port is updated? Many people, including myself are using /usr/local/etc/php-fpm.d directory = to store pool configs (ending with *.conf) inside which we already named (maybe differently, not everybody uses www.conf, plenty of people surely use domainname.conf or similar) and upgrading port and restarting service cause= s it to load another pool which is not being used at all thus wastes resources a= nd generally annoys. Port upgrading already creates www.conf.default which is identical to www.c= onf so there's no really a reason for 2 identical files to coexist. I propose removing www.conf and leaving www.conf.default as a reference to those who want to create their own pool configs out of it. --=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-210584-13>