Hi, sorry for my late response
David Relson wrote:
I run several low traffic lists (rarely more than 10 messages per day
and fewer than 250 users per list). I'd worry about a restart while
mailman is in operation. Not knowing the code, there _could_ be
problems in nuking it unexpectedly. With my
On Thu, 18 Nov 2004 07:23:27 -0500 (EST)
Sean wrote:
> > > I still want to solve the problem, but meanwhile, would
> > > there be
> > > any negative effect to adding an hourly cron job to restart
> > > mailmanctl? Or perhaps to run a script to check that
> > > /var/lib/mailman/data
> > I still want to solve the problem, but meanwhile, would there be
> > any negative effect to adding an hourly cron job to restart
> > mailmanctl? Or perhaps to run a script to check that
> > /var/lib/mailman/data/master-qrunner.pid is a valid process ID, else
> > restart mailmanctl?
>
At 11:29 AM -0500 2004-11-17, Steven J. Owens wrote:
Even with -auxw I get nothing.
You may need to toss in a second "w". I know that I need to do
this on some of the systems I admin.
Where is mailmanctl normally supposed to be started from? I
don't see any reference to mailmanctl
Mark,
On Tue, Nov 16, 2004 at 01:54:17PM -0800, Mark Sapiro wrote:
> >I can't see a mailmanctl daemon with:
> > ps -aux| grep mailmanctl |grep -v grep
>
> Note that on Red Hat 7.3, with an 80 column screen, I have to do
> ps -auxw| grep mailmanctl |grep -v grep
> in order to see anythin
Steven J. Owens wrote:
>
>In any event, both /var/lib/mailman/bin/version and "dpkg -l mailman"
>says I'm running 2.1.5 (dpkg says 2.1.5.3), and this section of the
>FAQ says:
>
> If you are running Mailman 2.1.x then the qrunners are daemons that
> are started by $prefix/bin/mailmanctl, which
Hi,
Mailman seems to randomly stop sending messages.
I'm running:
debian woody
postfix 2.1.3-1
mailman 2.1.5
python 2.3.4-1
My only real suspect is that either mailmanctl isn't being started, or
that bad lock files are being built up in the lock directory.
Restarting mail
