Public bug reported:
The version of Mailman distributed with Apple's Mac OS X Server has a hacked up mailmanctl, primarily to support not daemonizing in the launchd environment. (I think). Their hack is ugly, and it'd be nice if it was made unnecessary.
** Affects: mailman Importance: Undecided Status: New
I'm supportive of adding a --no-daemonize option (or equivalent) to the Mailman 3 'bin/mailman start' command.
** Changed in: mailman Status: New => Triaged
** Changed in: mailman Importance: Undecided => Medium
** Changed in: mailman Milestone: None => 3.0.0a5
** Also affects: mailman/3.0 Importance: Medium Status: Triaged
** Changed in: mailman/3.0 Milestone: 3.0.0a5 => None
I haven't yet gotten my hands on a copy of Mac OS X Server 10.6, but am hoping to do so early next year. If that materializes, I can take another look at what atrocities Apple may have committed, and report back.
** Tags added: mailman3
I've decided to set this to Won't Fix because in Mailman 3, bin/mailman start is little more than a wrapper around bin/master, which does not daemonize. This has all been refactored for simplicity so if you really wanted a no-daemonizing 'bin/mailman start', you really should just be calling 'bin/master' instead.
** Changed in: mailman/3.0 Status: Triaged => Won't Fix
** Changed in: mailman Status: Triaged => Won't Fix