Wietse Venema via Postfix-users wrote in <4q2l0p03svzj...@spike.porcupine.org>: |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-postgr\ |>|>|> ay\ |>|>|>: \ |>|>|> process id 8486: command time limit exceeded ... |>|>|> log messages, which they did not do in the past. I find this ... |>|> Is there a reason this happens now? I mean, that policy thing is ... |>|The spawn daemon has always worked this way. Below is a sample from ... |> 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.
Hm. Well maybe i simply have not seen the messages in the past, the logs rotate so fast, the only message still there is from "Apr 19 14:43:56", and when i checked my thing via postfix logs i, ..., hm. I really have never seen such a message, consciously. Then sorry for the noise. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
