[Bug 193621] New: fail2ban doesn't use syslog correctly-patch attached
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Sep 13 22:40:06 UTC 2014
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 at FreeBSD.org
Reporter: dewayne at 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 at 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.
More information about the freebsd-ports-bugs
mailing list