Fix: Reduce the aggresive default /var/cron/tabs/mailman entries below: # Every 5 mins, try to gate news to maila \ . You can comment this one out 0,5,10,15,20,25,30,35,40,45,50,55 * * * * \ /usr/local/bin/python2.2 -S /usr/local/mailman/cron/gate_news # Retry failed deliveries once per minute. * * * * * /usr/local/bin/python2.2 -S \ /usr/local/mailman/cron/qrunner Comment out gate_news by default, to match the admin web page, which also has news gating off by default. Change qrunner to 5 * * * * or 10 * * * * The few people that want a fast list can reduce it manually. An agressive 1 minute machine thrasher is not nice. How-To-Repeat: cd /usr/ports/mail/mailman; xs make install on any slow or loaded machine, where presumably the qrunner takes longer than one minute to run, wait for qrunners to build up, the disc to thrash, & finally if you don't catch it in time, you cant even remote login in to reboot, as ssh times out. A pruned `ps -laxww is appended' -------- UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 291 109 14 -6 0 1040 72 piperd I ?? 0:00.09 cron: running job (cron) 91 292 291 44 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 293 292 94 39 0 4832 808 - R ?? 0:33.51 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 0 296 109 13 -6 0 1040 72 piperd I ?? 0:00.07 cron: running job (cron) 0 297 109 11 -6 0 1040 72 piperd I ?? 0:00.08 cron: running job (cron) 91 298 297 45 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/gate_news 91 299 296 45 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 302 298 100 40 0 4488 1060 - R ?? 0:24.39 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/gate_news 91 303 299 119 42 0 4452 1144 - R ?? 0:24.82 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 0 307 109 101 -6 0 1040 72 piperd I ?? 0:00.06 cron: running job (cron) 91 309 307 130 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 310 309 100 40 0 4064 836 - R ?? 0:18.46 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 0 314 109 13 -6 0 1040 72 piperd I ?? 0:00.08 cron: running job (cron) 91 315 314 55 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 316 315 94 39 0 2864 1024 - R ?? 0:12.68 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 0 324 109 76 -6 0 1040 76 piperd I ?? 0:00.06 cron: running job (cron) 91 325 324 115 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 326 325 109 -22 0 2440 920 - RL ?? 0:08.68 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 0 333 109 14 -6 0 1040 76 piperd I ?? 0:00.07 cron: running job (cron) 91 334 333 52 10 0 628 0 wait IWs ?? 0:00.00 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 335 334 104 41 0 2224 876 - R ?? 0:04.16 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 0 340 109 15 -6 0 1040 260 piperd S ?? 0:00.10 cron: running job (cron) 0 341 109 19 -6 0 1040 252 piperd S ?? 0:00.11 cron: running job (cron) 91 342 340 59 10 0 628 68 wait Ss ?? 0:00.42 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner 91 343 341 60 10 0 628 60 wait Ss ?? 0:00.44 /bin/sh -c /usr/local/bin/python2.2 -S /usr/local/mailman/cron/gate_news 91 345 343 89 39 0 1892 852 - R ?? 0:00.69 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/gate_news 91 346 342 88 39 0 1892 888 - R ?? 0:00.70 /usr/local/bin/python2.2 -S /usr/local/mailman/cron/qrunner --------
Responsible Changed From-To: freebsd-ports-bugs->wjv Over to the maintainer.
Adding to the audit trail: : Message-Id: <20030409073717.GA15407@fling.sanbi.ac.za> : Date: Wed, 9 Apr 2003 09:37:18 +0200 : From: Johann Visagie <wjv@FreeBSD.org> : : Julian Stacey on 2003-04-08 (Tue) at 22:54:13 +0200: : > Reduce the aggresive default /var/cron/tabs/mailman entries below: : > # Every 5 mins, try to gate news to maila \ : > . You can comment this one out : > 0,5,10,15,20,25,30,35,40,45,50,55 * * * * \ : > /usr/local/bin/python2.2 -S /usr/local/mailman/cron/gate_news : > : > # Retry failed deliveries once per minute. : > * * * * * /usr/local/bin/python2.2 -S \ : > /usr/local/mailman/cron/qrunner : > : > Comment out gate_news by default, to match the admin web page, which : > also has news gating off by default. : > : > Change qrunner to 5 * * * * or 10 * * * * : > The few people that want a fast list can reduce it manually. : > An agressive 1 minute machine thrasher is not nice. : : While I agree with the argument, I should point out that mail/mailman : merely installs the crontab as distributed with Mailman, and thereby : emulates a user following instructions in Mailman's INSTALL file to : the letter whilst doing a manual install. : : Shouldn't this matter rather be taken up with the Mailman developers, : rather than trying to fix it in ports? : :----------------------------------------------------------------------- : : Message-Id: <200304091043.h39AhR141533@flip.jhs.private> : Date: Wed, 09 Apr 2003 12:43:27 +0200 : From: "Julian H. Stacey" <jhs@berklix.com> : : Johann Visagie wrote: : > While I agree with the argument, I should point out that : > mail/mailman merely installs the crontab as distributed with : > Mailman, and thereby emulates a user following instructions in : > Mailman's INSTALL file to the letter whilst doing a manual install. : > : > Shouldn't this matter rather be taken up with the Mailman : > developers, rather than trying to fix it in ports? : : Thanks. Yes, it would be best if Mailman developers fix their generic : in their next release if they want to. (If they don't I'd appreciate : if you patch it for FreeBSD later though). I haven't contacted the : Mailman developers [yet]: As the designated MAINTAINER= in Makefile, I : thought I'd funnel it through you first (but send-pr it too, as it : literaly killed all my server net connectivity). Should I contact : Mailman developers or will you ? (I'd prefer you to, if willing ? :-)
Responsible Changed From-To: wjv->nork I'll handle this.
State Changed From-To: open->closed Maybe fixed.