On Fri, 15 Nov 2024, Luca Bertoncello via Exim-users wrote:
> I always used a start script that started these instances:
>
> start-stop-daemon --start --pidfile /var/run/exim1.pid --quiet
> --exec $DAEMON -- "-bd"
> echo "exim runner 1"
> start-stop-daemon --start --pidfile /var/run/exim2.pid --quiet
> --exec $DAEMON -- "-q 5m"
> echo "exim runner 2"
> start-stop-daemon --start --pidfile /var/run/exim3.pid --quiet
> --exec $DAEMON -- "-qff 1h"
> Am 15.11.2024 um 15:34 schrieb Jeremy Harris via Exim-users:
>> On 15/11/2024 14:09, Luca Bertoncello via Exim-users wrote:
>>> What am I doing wrong this time?
>>
>> Misreading the documentation?
>>
>> The time value needs to be part of the -q option.
No space between -qff and the time interval.
eg -q5m and -qff1h
>> Also, there is little point in having your receiving daemon
>> separate from your main queue-runner daemon.
> Sorry, I really don't understand what you mean...
> Could you please explain, maybe with a little example?
What is wrong with just
start-stop-daemon --start --quiet --exec $DAEMON -- "-bd" "-q5m"
?
The exim daemon is designed to accept deliveries and do queue runs;
there is normally no need for these to be eparate processes.
*If* you really need a separate queue runner for frozen messages
give that one a separate pid-file, but the other one can just use the
default.
Messages are only frozen if they fail *and* the failure cannot be
reported back to the sender. If there are frozen messages, you should
probably investigate them.
--
Andrew C. Aitchison Kendal, UK
andrew@???
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
