Ondrej, I have some questions
Why were the old courier init scripts discarded in favor of using the init-d-script method/system? Were there some bugs related to them which needed to get fixed? And, was there a particular reason why the init-d-script method was used over writing stand-alone init scripts?
Historically, Courier uses it's environment to determine configuration parameters, which, admittedly, is weird/questionable/ugly. All of those config files in /etc/courier are just shell fragments specifying parameters. The old init scripts sourced those parameters into the environment before execution and passed them down. Additionally, daemons were customarily executed as part of a pipeline involving courierlogger and couriertcpd. The new init scripts don't do this. Was that on purpose, or were you unaware of any of this?
Before I propose any changes, I'd like to find out what your ideas were. On 04/21/2016 02:38 AM, Ondřej Surý wrote:
Please read /lib/init/init-d-script (and /usr/lib/courier/init-d-script-courier) first and then come back again.
