Quanah,
>> [pid 31204] 12:00:38.491431 write(3, "\25\3\1\0
>> \0c\337\2P\225G\215\6\21\362\363P\277T\25\231Ms\27W\332
>> \321\31\200\26\5"...,
>> 37) = -1 EPIPE (Broken pipe)
> Turns out this is due to a buggy release of nss_ldap that RHEL pushed.
>
> https://bugzilla.redhat.com/show_bug.cgi?i
--On Monday, June 23, 2008 9:10 AM -0700 Quanah Gibson-Mount
<[EMAIL PROTECTED]> wrote:
> --On Thursday, June 19, 2008 12:25 PM +0200 Mark Martinec
> <[EMAIL PROTECTED]> wrote:
>
>>> Since debug mode works, it's hard to gather data on why children won't
>>> fork. Any thoughts?
>>
>> Was the abov
--On Thursday, June 19, 2008 12:25 PM +0200 Mark Martinec
<[EMAIL PROTECTED]> wrote:
>> Since debug mode works, it's hard to gather data on why children won't
>> fork. Any thoughts?
>
> Was the above strace/truss collected with an -f option?
> If not, it should be, as apparently the problem is i
Quanah,
> After doing a yum update on a RHEL5 box to take it to update 2, Amavis
> fails to start if it is not in debug mode. The difference appears to be
> that in debug mode, Amavis never forks.
You are probably referring to the fork during daemonization,
which indeed is skipped in debug mode.
After doing a yum update on a RHEL5 box to take it to update 2, Amavis
fails to start if it is not in debug mode. The difference appears to be
that in debug mode, Amavis never forks. When running outside of debug
mode, Amavis fails to fork a child, so thus refuses to start:
stat("/opt/zimbra/
