On 8/28/10 10:47 AM, Steve Burling at s...@umich.edu wrote: > --On August 28, 2010 10:32:15 AM -0500 Brad Knowles > <b...@shub-internet.org> wrote: > >> After that, we might think about whether or not we can, or should, go >> after Apple. Both companies are shipping our code with extensive >> modifications, and so far as I know neither of them has released their >> changes, as required by the GNU license. > > To which I reply: > > For what it's worth, I dif'd Apple's Mailman code against the stock code at > one point, and I wouldn't describe the changes as extensive. The primary > change was the addition of a version of 'mailmanctl start' that wouldn't > daemonize, in order to work properly with Apple's launchd.
I know I've mentioned this before but worth repeating. I run Mailman built from source on Mac OS X Client. Startup was a problem because of daemonizing but more or less solved by having launchd run a script that ran 'mailmanctl start' and then waited a second before exiting. Trying to run 'mailmanctl start' directly from the launchd plist tended to fail due to the launchd process exiting before mailman could daemonize. Since it daemonizes, launchd can't monitor it (it's 'Run at Load' and then launchd is out of the picture) so I deal with Mailman dying on me by having an hourly cron job that checks for the proper number of qrunners and sends me mail if it's wrong (Mailman is far, far from mission critical in my environment). -- Larry Stone lston...@stonejongleux.com http://www.stonejongleux.com/ ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
