Re: Qmail/MailMan - Crashing Children with no cause.
Search the archives for preline and SIGPIPE. I think you'll find the answer there. Regards. On Mon, Jul 02, 2001 at 03:33:20PM -0700, Alex Hathaway allegedly wrote: This is an odd ball error: deferral: preline:_fatal:_child_crashed/ I'm using mailman as a list agent (ezmlm is nice, but a bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
RE: Qmail/MailMan - Crashing Children with no cause.
I don't think that's the problem.. To quote Dan, The next version of preline will work just like a pipe from the shell: it will put the main command in the foreground, and it will die silently if it receives SIGPIPE. ---Dan I even to speculation, used the patch in the archives with still the same result. *pullig heair out* why can appy's just get along? -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Qmail/MailMan - Crashing Children with no cause. Search the archives for preline and SIGPIPE. I think you'll find the answer there. Regards. On Mon, Jul 02, 2001 at 03:33:20PM -0700, Alex Hathaway allegedly wrote: This is an odd ball error: deferral: preline:_fatal:_child_crashed/ I'm using mailman as a list agent (ezmlm is nice, but a bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
Re: Qmail/MailMan - Crashing Children with no cause.
On Mon, Jul 02, 2001 at 04:29:50PM -0700, Alex Hathaway allegedly wrote: I don't think that's the problem.. To quote Dan, The next version of preline will work just like a pipe from the shell: it will put the main command in the foreground, and it will die silently if it receives SIGPIPE. Right. But that next version isn't out yet. Your point is? I even to speculation, used the patch in the archives with still the same result. *pullig heair out* why can appy's just get along? You're being silly. You don't know the reason for your problem, yet when someone offers a solution you dismiss it for no good reason and without even trying it! Sounds like you enjoy *pullig heair out* (sic). Regards. -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Qmail/MailMan - Crashing Children with no cause. Search the archives for preline and SIGPIPE. I think you'll find the answer there. Regards. On Mon, Jul 02, 2001 at 03:33:20PM -0700, Alex Hathaway allegedly wrote: This is an odd ball error: deferral: preline:_fatal:_child_crashed/ I'm using mailman as a list agent (ezmlm is nice, but a bit short of my needs) and for some reason when passing info through preline this error pops up in the syslog. However if I pipe the mail message direct to the command itself without preline or qmail, I get a message just fine. the line in the .qmail- file reads: |/var/qmail/bin/preline /usr/local/mailman/mail/wrapper mailcmd timy As much as I would like to say it's all mailmans fault, I can't figure why it would die via only qmail, and not the command line. I'm on Solaris X86 ver 8 Using roaming users, and vchkpwd. Any ideas of things to try or how to debug would be very helpful and appreachiated -Alex
