With PIDFile=/run/imapproxy.pid, I get the following errors: PID file /run/imapproxy.pid not readable (yet?) after start: No such file or directory
Supervising process 824 which is not our child. We'll most likely not notice when it exits. >From my first testing, it worked fine without PIDFile. Unfortunately, upon further testing, it seems to fail most of the time. Given that those errors seem harmless, I think setting PIDFile is the lesser of the two evils right now, so I'm sticking with that. I've sent the update to my sponsor. (I'm not a DD.) I should probably explore the idea of adding a command-line option to imapproxy that sets foreground_mode. Then, I can use that in the systemd unit, making this Type=simple instead of Type=forking. -- Richard
