Re: [Exim] mailman

Kezdőlap
Üzenet törlése
Válasz az üzenetre
Szerző: Mark Symonds
Dátum:  
Címzett: Michael Stevens, Milos Prudek
CC: exim-users
Tárgy: Re: [Exim] mailman

----- Original Message -----
From: "Michael Stevens" <mstevens@???>
To: "Milos Prudek" <prudek@???>
Cc: "Mark Symonds" <mark@???>; <exim-users@???>
Sent: Tuesday, January 18, 2000 2:47 AM
Subject: Re: [Exim] mailman


> On Tue, Jan 18, 2000 at 07:42:46AM +0100, Milos Prudek wrote:
> > > Perhaps mailman somehow doesn't like exim?
> > No no, this list itself is run by mailman and exim.
>
> I've successfully used mailman and exim together. I had problems with
> mailman later and stopped using it, but I don't see any reason to
> think it was related to exim.
>


Yes -- at least in my situation it was definitely a mailman
problem all the way. Exim had nothing to do with it.

I found this in /var/lib/mailman/cron/crontab.in:

# Every 5 mins, try to gate news to mail. You can comment this one out
# if you don't want to allow gating, or don't have any going on right now,
# or want to exclusively use a callback strategy instead of polling.
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python
/var/lib/mailman/cron/gate_news
#

...that line wasn't commented although I had told mailman
via the admin web interface not to gate news/mail.

Anyway it's been well over 12 hours without a problem,
no wild /USR/CRON processes anymore.

Just thought I'd post that in case anyone else runs into it,
sorry for being a bit off-topic.

-Mark

-----
"I know everything we've done is absolutely right and proper"
                --Microsoft CEO Steve Ballmer on MSNBC, 01/13/00
-----



----- Original Message -----
From: "Mark Symonds" <mark@???>
To: "Debian" <debian-user@???>
Sent: Monday, January 17, 2000 6:31 PM
Subject: Perplexing mailman situation


>
> Hi, I'm a bit new to Debian so forgive me if this is
> a FAQ, but I installed mailman last night via apt-get
> and everything seemed to be working beautifully
> until I checked the machine this morning and discovered
> the filesystem was ro. The logs said that there was
> an attempt to access beyond the end of /dev/hda1
> so I ran e2fsck, fixed the errors and finally put the
> drive back in rw.
>
> Everything went smoothly until 12 hours later
> the server started dying and I noticed the average load
> had begun climbing through the roof. A ps aux revealed
> about 100 instances of /USR/CRON running!