Date: Sat, 13 Sep 2014 22:40:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193621] New: fail2ban doesn't use syslog correctly-patch attached Message-ID: <bug-193621-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193621 Bug ID: 193621 Summary: fail2ban doesn't use syslog correctly-patch attached Product: Ports Tree Version: Latest Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: dewayne@heuristicsystems.com.au Created attachment 147288 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147288&action=edit Patch to server/server.py fail2ban uses /dev/log rather than /var/run/log, per an email from stavros@staff.esc.net.au. As we're just starting integration testing we thought we'd enhance the application with Stavros suggestion (Thank-you for sharing). There are two server.py's in the distfile, the patch's name identifies which one. Upstream should address, however in the interim, please refer to patch. -- 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-193621-13>