Hide Forgot
Description of problem: Upon starting the imapproxy service, up-imapproxy's init script does not fork imapproxy to the background Version-Release number of selected component (if applicable): up-imapproxy-1.2.6-1.el5 How reproducible: Every time Steps to Reproduce: 1. Install up-imapproxy 2. Configure if necessary 3. # /sbin/service imapproxy start Actual results: Does not return to the command-line and "hangs" indefinitely. Expected results: Return to cli Additional info:
I strongly suspect there is something about your environment or configuration that is causing it to hang, rather than a fault in the init script (since it's pretty straightforward). Have you discussed the problem on the imapproxy mailing list?
Could you elaborate on what kind of environment / system setting would / could be of influence on what I consider to be a clean install? I have contacted the original author, Dave McMurtrie, as he's somewhat closeby given that I'm the release engineer for Cyrus IMAP and Cyrus SASL. Thanks.
I can't suggest anything specific assuming that you've eliminated things such as any firewalls that could be blocking the proxy startup when it tries to connect out. It's just that the package has been around for a while and there's nothing unusual in the init script (all it does is "daemon /usr/sbin/in.imapproxyd"), and it isn't reproducible for me on a clean install. Is there anything special you need to do to reproduce it?
Works for me. If you still have this problem, please consider seeking help on the upstream mailing list, and if it turns out to be a problem with the packaging then please re-open this bug.