Re: [courier-users] Failed filter restarts when restarting courier and filter times out when stopping

2015-01-09 Thread Sam Varshavchik
Alessandro Vesely writes: Currently, the shutdown code just gives up, after a timeout, in this manner. I do agree that an attempt should be made to kill all processes, after a reasonable timeout, so it's something that I need to look at. To kill by pid is going to be difficult for forked

Re: [courier-users] Failed filter restarts when restarting courier and filter times out when stopping

2015-01-09 Thread Gordon Messmer
On 01/09/2015 01:06 PM, Jeff Potter wrote: We have to restart courier many times a day to pick up changes to files under the aliases dir and esmtpacceptmailfor You shouldn't have to restart anything for those two. The man page for courier states, Unless otherwise specified, you must run

Re: [courier-users] Failed filter restarts when restarting courier and filter times out when stopping

2015-01-09 Thread Alessandro Vesely
On Thu 08/Jan/2015 23:51:56 +0100 Jeff Potter wrote: 4. After start, pythonfilter is not started — 'filterctl start pythonfilter' fails to bring it up with this: filterctl start pythonfilter ln: creating symbolic link `/etc/courier/filters/active/pythonfilter' to