SW:
> Hi Wietse, many thanks for the reply.
>
> egrep '(warning|error|fatal|panic):' /var/log/postfix/maillog | more gives:
>
> Feb 15 05:13:57 mail postfix/master[88477]: warning: process
> /usr/local/libexec/postfix/smtpd pid 40297 killed by signal 11
> Feb 15 05:13:57 mail postfix/master[88477]: warning:
> /usr/local/libexec/postfix/smtpd: bad command startup -- throttling
> Feb 15 05:42:49 mail postfix/master[88477]: warning: process
> /usr/local/libexec/postfix/smtpd pid 48696 killed by signal 11
> Feb 15 05:42:49 mail postfix/master[88477]: warning:
> /usr/local/libexec/postfix/smtpd: bad command startup -- throttling
OK, looks clean.
> I have added the following to main.cf:
>
> debugger_command =
> PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; echo
> where; sleep 8640000) | gdb $daemon_directory/$process_name
> $process_id 2>&1
> >$config_directory/$process_name.$process_id.log & sleep 5
>
> and changed master.cf to:
>
> smtpd pass - - n - - smtpd -D
>
> and restarted Postfix.
>
> Do I just wait now until Postfix crashes again? Where is the crash log
> stored?
You determine the location of the debugger output file as follows:
1) Postfix removes empty lines and newline characters that are
followed by whitespace. Thus, debugger_command is one line of text
that is given to a shell process.
2) In the debugger_command line, Postfix replaces $name with the
corresponding Postfix parameter value. See "man 5 postconf" for
a description of parameters.
3) Postfix executes the command. See "man sh" for a description of
the '>' operator.
Wietse
