Harald Hanche-Olsen wrote:
> Your qmail-send trace is more interesting. It shows qmail-send
> detecting a pending bounce for message 313551, then setting up pipes
> and forking, the child trying but failing to run qmail-queue in order
> to inject the bounce message. You should look at the permissions on
> qmail-queue (should be -rws--x--x I think). But what is really odd is
> that qmail-send (the parent) segfaults, apparently even before the
> child exits (even before it has started writing any data to the pipe).
> If you fix the permission problem with qmail-queue, maybe this other
> problem goes away.
>
> Summary:
> - Make sure qmail-queue has the right permissions.
[root@localhost qmail]# ls -l /var/qmail/bin/qmail-queue
-rwsr-xr-x 1 qmailq qmail 10508 May 20 22:17
/var/qmail/bin/qmail-queue
Also, 'make check' and qmail-lint have no complaints.
> - Look at your patches with a great dose of skeptisism.
Ok, will do. This is probably the most likely source for the problem. "If
you eliminate the impossible...." as Sherlock said.
> - Perhaps worry about the fork vs vfork issue
> (about which I know next to nothing, but if problems in child
> process interfere with the parent, I would suspect vfork (but fork
> and vfork are the same on at least some systems)).
All I know is that in Linux, vfork is merely an alias for fork. I haven't
played with any qmail forks. Only knives ;-)
> - If all fails, maybe abandon your patches and move to qmail 1.03.
I sure will, but not for the time being. I will have to apply the patches
to v1.03 as well and this will take too long time to do now.
Anyway, thanks to Harald and all others who helped me! If you have no
more comments to add to the above, I will put on my hard hat and start
digging.
Cheers :-)
Fred
