ports/110695: Trouble when using imapproxyd with imap-uw
João Carlos Mendes Luís
jonny at jonny.eng.br
Fri Mar 23 05:20:04 UTC 2007
>Number: 110695
>Category: ports
>Synopsis: Trouble when using imapproxyd with imap-uw
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Mar 23 05:20:03 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: João Carlos Mendes Luís
>Release: FreeBSD 6.2-STABLE i386
>Organization:
>Environment:
System: FreeBSD roma.coe.ufrj.br 6.2-STABLE FreeBSD 6.2-STABLE #4: Thu Mar 22 23:37:54 BRT 2007 Jonny at roma.coe.ufrj.br:/usr/cvsup/RELENG_6/src/sys/i386/compile/ROMA i386
>Description:
In my server, I noticed imapproxyd never started on boot, I had to start
it manually. Today I found it needs the main imap server to be online
when it starts.
My configuration is to use imap-uw inside inetd. imapproxyd was starting
before inetd, and therefore, imap server was not already online, ending
in error.
>How-To-Repeat:
Install imapproxyd and any inetd based imap server.
>Fix:
imapproxyd startup script seems to be create to be used with courier
and cyrus, but completely forgot inetd based servers.
I just added inetd into the REQUIRE list, and it solved my problem.
Now, the dependencies for rcorder are like this:
# PROVIDE: imapproxyd
# REQUIRE: DAEMON courier_imap_imapd courier_imap_imapd_ssl cyrus_imapd inetd
# KEYWORD: shutdown
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list