Steffen Nurpmeso:
> Wietse Venema wrote in
> <4q21sp16m7zj...@spike.porcupine.org>:
> |Steffen Nurpmeso via Postfix-users:
> |> On 3.8.0 services managed via spawn(8) now produce
> |>
> |> Apr 19 01:03:04 postfix/spawn[8485]: warning: /usr/libexec/s-postgray: \
> |> process id 8486: command time limit exceeded
> |> Apr 19 14:43:56 postfix/spawn[19651]: warning: /usr/libexec/s-postgray:\
> |> process id 19755: command time limit exceeded
> |>
> |> log messages, which they did not do in the past. I find this
> |> irritating, because the service works properly, it does not "hang"
> |> or fails to give answers, for example:
> |
> |The time limit is configured in main.cf.
> |
> |You need to figure out the name of the correspnding master.cf
> |entry, and then add a configuration parameter with that name:
> |
> |main.cf:
> | *name*_time_limit = some suitable number
>
> Is there a reason this happens now? I mean, that policy thing is
> waiting for postfix to ask it something, not vice versa?
> But ok, will do. Thanks.
The spawn daemon has always worked this way. Below is a sample from
the Postfix 2.1.0 SMTPD_POLICY_README file, almost 20 years ago.
Wietse
1 /etc/postfix/master.cf:
2 policy unix - n n - - spawn
3 user=nobody argv=/some/where/policy-server
4
5 /etc/postfix/main.cf:
6 smtpd_recipient_restrictions =
7 ...
8 reject_unauth_destination
9 check_policy_service unix:private/policy
10 ...
11 policy_time_limit = 3600
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
