Opened 8 years ago
Last modified 5 years ago
#53578 assigned defect
fail2ban @0.9.3 doesn't install plist during installation or configuration
| Reported by: | blgantner (Brennan Gantner) | Owned by: | |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 2.4.0 |
| Keywords: | Cc: | ||
| Port: | fail2ban |
Description
OS: ElCap and Sierra, Xcode: 8.2.1
After installation of fail2ban, command "sudo port load fail2ban" fails due to the .plist not being copied or linked to in /Library/LaunchDaemons/. Found this same error in two computers (one Sierra, one ElCap, both same macports 2.4.0 and fail2ban 0.9.3). In both cases, I copied the plist present in the macports tree to /Library/LaunchDaemons manually and it loaded and ran correctly.
sudo port load fail2ban Password: Error: Failed to load fail2ban: Launchd plist /Library/LaunchDaemons/org.macports.fail2ban.plist was not found
Change History (3)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
| Cc: | fclaire@… removed |
|---|---|
| Owner: | set to fclaire@… |
| Status: | new → assigned |
comment:2 Changed 8 years ago by blgantner (Brennan Gantner)
comment:3 Changed 5 years ago by kurthindenburg (Kurt Hindenburg)
| Owner: | fclaire@… deleted |
|---|
Note: See
TracTickets for help on using
tickets.
As an addition that I just thought of, macports on both computers is set up to install in a custom directory without su needed to install ports. This is likely why it couldn't create/link to /Library/LaunchDaemons. However, it did not produce any error or warning of that failure. This may be the actual bug.