v1.2.2. contains performance fixes and most importantly a default listen_to config option !! - now it listens to 0.0.0.0 - and I have to firewall it. Most people only use it for local cache for their squirrelmail or other webmail - and so one should be able to set it to listen to localhost ONLY. with 1.2.2 you can now do that. I just renamed the ebuild to 1.2.2 and it works just fine. the init-script doesn't stop the imapproxy though - so when giving it a restart - it just says stopping and never starting - because it fails to stop it(but thats with the script that is used in v1.2.1). Reproducible: Always Steps to Reproduce: 1. 2. 3.
Bumped in CVS portage. The initscript actually works, but new version spawns three processes. After start-stop-daemon kills the first one, other two die with it, and when start-stop-daemon tries to kill them, it fails, since they're already dead: # ps ax|grep imap 29145 ? S 0:00 /usr/sbin/imapproxyd 29147 ? S 0:00 /usr/sbin/imapproxyd 29148 ? S 0:00 /usr/sbin/imapproxyd 29151 pts/80 R+ 0:00 grep imap root@thelair /etc/init.d # /etc/init.d/imapproxy stop * Stopping imapproxy... start-stop-daemon: warning: failed to kill 29147: No such process start-stop-daemon: warning: failed to kill 29145: No such process [ ok ] root@thelair /etc/init.d # ps ax|grep imap 29195 pts/80 R+ 0:00 grep imap root@thelair /etc/init.d # I guess we should bug maintainers of baselayout about this, CCing them to get their opinion.
start-stop-daemon can only do so much when it comes to guessing at the PID in this case, it looks like: proxy starts up and start-stop-daemon records this pid proxy forks off children then exits start-stop-daemon tries to kill the parent pid that exited already either way, not a start-stop-daemon bug; handle the stopping of the proxy some other way
The initscript works for me now, as it only runs one process, not three. I haven't changed anything related in the config. Closing, thanks for reporting.
