Dangers of modifying preline.c

2001-07-10 Thread Alex Hathaway

Is there any dangers in commenting out the lines:

/*  if (wait_crashed(wstat))
strerr_die2x(111,FATAL,child crashed); */

in preline.c ?



Qmail/MailMan - Crashing Children with no cause.

2001-07-02 Thread Alex Hathaway



This 
is an odd ball error:

"deferral: preline:_fatal:_child_crashed/"

I'm 
using mailman as a list agent (ezmlm is nice, buta 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.

2001-07-02 Thread Alex Hathaway

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: Connection refused - but not really...

2001-06-29 Thread Alex Hathaway

screams dns, but not really. Very odd.
I'd take down the FW long enough to make sure it's not the cause, then start
looking for DNS issues. Usually something that won't work for a while then
suddenly starts working screams a DNS server is resolving 1/2 the time.

-Original Message-
From: Tom Yarrish [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 7:24 AM
To: [EMAIL PROTECTED]
Subject: Connection refused - but not really...


Hey all,
I'm a newcomer to the list, but I've been using qmail for about a year or
so.  Recently my original qmail server (RH 6.2 - Sparc) died (bad memory)
and in a rush I built a new qmail server on another machine (RH 7.1 -
486).  The server seems to run fine, no error and such.  The way my system
is setup is that I have my hosting company forward any mail for my
yarrish.com domain to my mail server behind my firewall.  So I'm only
allowing this one machine to connect to my qmail server.  I've noticed
lately that I'm getting mail in bursts.  Meaning I'll get 40 messages at
one point, and then nothing for a certain amount of time (it's not
consistent as far as I can tell).  Then I'll get another 20-50 messages or
so.  So what I did as a test, was to allow one of my shell accounts to
access port 25 of my qmail server via my firewall.  So what happens is
when I try to telnet to my ip on port 25, I'll get a number of connection
refused (the number varies) and then I'll connect.  Once I connect, I can
disconnect and reconnect without any problems.  Then if I wait a while and
try again, the problem repeats itself.  This never happened before on my
old mail server.
I've talked to my hosting company, and their logs are showing the same
timeout message and then connect.  Also, if I try to connect from one of
my other machines on the same network as my qmail server, the connection
is not refused.  My firewall logs are not showing the packet being dropped
(and normally it would, I've tested that as well).  Now I have order a new
network card, just to eliminate that possibility (I don't know how old the
card in the qmail server currently is).  But I'm wondering if anyone else
can suggest something to look at, at least to eliminate the qmail server
being the problem.  I am going to fire up the old qmail server and see if
the problem is still there.
Here's my startup for smtpd:
#!/bin/sh
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
exec /usr/local/bin/softlimit -m 200 \
/usr/local/bin/tcpserver -v -o -P -H -R -llocalhost.localdomain -x
/etc/tcp.smtp.cdb -c $MAXSMTPD \
-u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd
21

Thanks ahead of time for any help.
Tom

--
#!/usr/bin/perl -w # 526-byte qrpff, Keith Winstein and Marc Horowitz
[EMAIL PROTECTED] # MPEG 2 PS VOB file on stdin - descrambled output
on stdout # arguments: title key bytes in least to most-significant order
$_='while(read+STDIN,$_,2048){$a=29;$c=142;if((@a=unxC*,$_)[20]48){$h=5;
$_=unxb24,join,@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$/;$d=
unxV,xb25,$_;$b=73;$e=256|(ord$b[4])9|ord$b[3];$d=$d8^($f=($t=255)($d
12^$d4^$d^$d/8))17,$e=$e8^($t($g=($q=$e147^$e)^$q*8^$q6))9
,$_=(map{$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])110;$t
^=(72,@z=(64,72,$a^=12*($_%16-2?0:$m17)),$b^=$_%64?12:0,@z)[$_%8]}(16..271)
)
[$_]^(($h=8)+=$f+(~$g$t))for@a[128..$#a]}print+xC*,@a}';s/x/pack+/g;eva
l