Date: Wed, 10 Dec 2014 12:13:28 +0100 From: Acheron Blackflow <acheron.blackflow@gmail.com> To: freebsd-ports@freebsd.org Subject: www/nginx: log littering Message-ID: <CAF_MnrFJ_kr%2BJPasK37orSZ1M92OhDhALX5=UtnbR-L8O340Qg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello list, any particular reason why default nginx logging is two files directly under /var/log, ie. /var/log/nginx-access.log and /var/log/nginx-error.log? Shouldn't nginx logging be nicely confined to the /var/log/nginx/ subdirectory? Even more so since nginx touches the default error log (--error-log-path compile time switch) regardless of the error_log directive in nginx.conf which then makes this impossible to keep clean by configuration alone. It's not just the inconvenience of tab completion being broken for /var/log/nginx with the /var/log/nginx-error.log always present. I am assuming most sysadmins would configure nginx logging under a dedicated directory anyway, primarily to keep the rotated files cleanly confined and not all over the parent /var/log/. I'd file that as a bug but seeing that nobody else complained (at least le Google is failing to return relevant ticket or ml post) I was wondering why that is?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF_MnrFJ_kr%2BJPasK37orSZ1M92OhDhALX5=UtnbR-L8O340Qg>