Other than modifying the #FreeBSD rc.d script each time fail2ban is updated, is there an easier way to ensure it does not start until after the jails are running?
see this 10 year old post - the problem persists:
https://forums.freebsd.org/threads/fail2ban-with-jails.49150/#post-650140
Dan Langille /
npub1an…5lewl
2024-09-08 00:53:51
Author Public Key
npub1an75uu9tk76kle0lgl7msn5egmtkd9aesv63cpngwxjpz7jap24sc5lewlPublished at
2024-09-08 00:53:51Event JSON
{
"id": "bae396b0eec25f2f8e0b49b96d33f12b1797d664337fb755a9f3135e78ef129a",
"pubkey": "ecfd4e70abb7b56fe5ff47fdb84e9946d76697b983351c066871a4117a5d0aab",
"created_at": 1725756831,
"kind": 1,
"tags": [
[
"t",
"freebsd"
],
[
"proxy",
"https://bsd.network/users/dvl/statuses/113099199733640098",
"activitypub"
]
],
"content": "Other than modifying the #FreeBSD rc.d script each time fail2ban is updated, is there an easier way to ensure it does not start until after the jails are running? \n\nsee this 10 year old post - the problem persists: \nhttps://forums.freebsd.org/threads/fail2ban-with-jails.49150/#post-650140",
"sig": "f6da04a8ba16577a300d19c31519bd22c23a61f5e5b96417d069ba9c96b063aafe68bded09557679b458c9f7be16021754872fc2d23a534f43d0214973e1f0d3"
}