Bug 244092 - security/py-fail2ban: Create required directoy on start
Summary: security/py-fail2ban: Create required directoy on start
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords: buildisok, feature, needs-qa
Depends on:
Blocks:
 
Reported: 2020-02-13 10:45 UTC by theis
Modified: 2020-02-17 12:42 UTC (History)
2 users (show)

See Also:
theis: maintainer-feedback+
koobs: merge-quarterly?


Attachments
patch (1.07 KB, patch)
2020-02-13 10:45 UTC, theis
theis: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description theis 2020-02-13 10:45:25 UTC
Created attachment 211607 [details]
patch

Reported at https://github.com/fail2ban/fail2ban/issues/2634
fail2ban should check and, if necessary create, the required directory.

It is still up to the user to ensure that configuration in fail2ban's conf files and FreeBSD's /etc/rc.conf are in sync and that both, pidfile and socket reside in the same directory

Thanks to Florian Koczan
Comment 1 Automation User 2020-02-13 11:05:26 UTC
Build info is available at https://gitlab.com/swills/freebsd-ports/pipelines/117564104
Comment 2 Steve Wills freebsd_committer 2020-02-16 13:59:10 UTC
This looks like a good addition. Have you considered adding -p ${pidfile} to the args, to avoid potential issues with mismatch between rc.conf and the fail2ban config?
Comment 3 theis 2020-02-17 12:41:50 UTC
I thought about that but may main problem is that users have to make sure the directories for pidfile and socket are the same, and here I'm running into conflicts trying to keep 2 configurations in sync. So I just wrote a hint about this.