Steffen Nurpmeso:
> Wietse Venema wrote in
>  <4q2khr57flzj...@spike.porcupine.org>:
>  |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-postgra\
>  |>|>   y:\
>  |>|>    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.
> 
> Yes, but it never logged it with a warning:, which is what this
> thread is about?  I am absolutely fine with postfix rotating the
> processes, but why warn about my little policy thing, and not
> about the postfix instance going home, too?

That code has not changed since it was written 23 years ago.

        Wietse

Postfix 1.0.0 spawn_command.c:

        if ((err = timed_waitpid(pid, &wait_status, 0, args.time_limit)) < 0
            && errno == ETIMEDOUT) {
            msg_warn("%s: process id %lu: command time limit exceeded",
                     args.command, (unsigned long) pid);
            kill(-pid, SIGKILL);
            err = waitpid(pid, &wait_status, 0);
        }

Postfix 3.8.0 spawn_command.c:

        if ((err = timed_waitpid(pid, &wait_status, 0, args.time_limit)) < 0
            && errno == ETIMEDOUT) {
            msg_warn("%s: process id %lu: command time limit exceeded",
                     args.command, (unsigned long) pid);
            kill(-pid, SIGKILL);
            err = waitpid(pid, &wait_status, 0);
        }

The last change in that file was in Postfix 3.0, and that was
a cosmetic change.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to