From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Thu Jan 24 2008 - 15:52:41 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Jan 24, 2008 at 01:41:19PM -0800, Ronald F. Guilmette wrote:

>
> OK. So let me see if I get this...
>
> The .forward file commands are, by default, initially cd'd into
> /var/spool/postfix, yes? But then if there is a signal 11 or other
> fatal unhandled signal, the kernel tries to write a .core file in
> the current directory, but since the command was executing under
> the user-id of the account whose home directory contained the .forward
> file, and since that user-id doesn't have write access to Postfix's
> /var/spool/postfix directory, no .core file is written.
>
> Correct so far?

Yes

> And the solution to this problem is to explicitly set, for example:
>
> command_execution_directory = $home
>
> in the main.cf file.

Yes, unless core file generation is disabled by some kernel tuning
parameter, default "ulimit" setting or core files are not written to
"core" in the current working directory, ...

This is somewhat platform dependent. For example, one RHEL 4 system has
the following in "sysctl -a" output:

    kernel.suid_dumpable = 0
    kernel.core_uses_pid = 0
    kernel.core_pattern = /var/tmp/cores/%e.%p.%u.core

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]