Bug 125655
| Summary: | Incorrect startup variable in mail/up-imapproxy rc.d/imapproxyd.sh | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Igor Roshchin <str> | ||||
| Component: | Individual Port(s) | Assignee: | Martin Blapp <mbr> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-ports-bugs->mbr Over to maintainer (via the GNATS Auto Assign Tool) I just tried to build the same port on 7.0-RELEASE and the (mis-)behavior is still there (obviously). The patch is simple. Please, review it and commit. State Changed From-To: open->closed Fixed via autoconf, thanks anyway |
/usr/local/etc/rc.d/imapproxyd.sh incorrectly uses imapproxyd_conf variable that is not being used by /etc/rc.subr: # imapproxyd_conf (file): Set location of conf file. # Default is "/usr/local/etc/imapproxyd.conf" Hence, this config file location is not being read by the program. As a result, the program looks for the hardcoded default: /etc/imapproxy.conf As far as I can tell, /etc/rc.subr does not contain ${name}_conf even on 6.x and 7.x systems (rev=1.86) One of the possibilities to correct this is to add imapproxyd_flags="-f ${imapproxyd_conf}" Fix: Here is the patch: How-To-Repeat: rm /etc/imapproxy.conf create /usr/local/etc/imapproxyd.conf reinstall port and try to start it, - it will not start.