Am/On Fri, 26 Jun 2009 13:49:57 +0200 schrieb/wrote Sebastian Hagedorn: >--On 26. Juni 2009 20:22:13 +0900 Matthias Schmidt <b...@admilon.net> wrote: > >> Am/On Thu, 18 Jun 2009 19:22:02 -0500 schrieb/wrote Larry Stone: >> >>> On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote: >>> >>>> I've built and installed Mailman 2.12 from current source code and >>>> have it running just fine under OS X Server 10.5.7, with on exception, >>>> which is not properly speaking a Mailman problem at all. >>>> >>>> If I start Mailman from the CLI, using /usr/share/mailman/bin/ >>>> mailmanctl -s start, all is well. >>>> >>>> If I allow launchd to start it >>>> S<caron>I get an endless succession ofS<caron> >>>> >>>> Jun 18 16:50:26 org.list.mailmanctl: Starting Mailman's master >>>> qrunner. >>>> Jun 18 16:50:26 com.apple.launchd (org.list.mailmanctl): >>>> Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python >>>> Jun 18 16:50:26 com.apple.launchd (org.list.mailmanctl): Throttling >>>> respawn: Will start in 9 seconds > >The reason this happens is that launchd expects the processes it launches >to stick around. They must not daemonize. But mailmanctl terminates after >it has started the runners. I assume that Apple modified their own >distribution of Mailman so that mailmanctl behaves differently. I'd suggest >comparing the two.
thanks, that was the information I missed and it also explains why Apple uses -startf in the plist, which is not documented for mailman. I meanwhile found out, that the voodoo here is to use mailmanctl from the original Apple distribution. cheers, Matthias ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9