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

--
Need a 'no-daemonize' option for '/bin/mailman start'
https://bugs.launchpad.net/bugs/497968
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

Search Discussions

  • Barry Warsaw at Dec 17, 2009 at 9:39 pm
    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

    --
    Need a 'no-daemonize' option for '/bin/mailman start'
    https://bugs.launchpad.net/bugs/497968
    You received this bug notification because you are a member of Mailman
    Coders, which is subscribed to GNU Mailman.
  • Steve Burling at Dec 17, 2009 at 9:49 pm
    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.

    --
    Need a 'no-daemonize' option for '/bin/mailman start'
    https://bugs.launchpad.net/bugs/497968
    You received this bug notification because you are a member of Mailman
    Coders, which is subscribed to GNU Mailman.
  • Barry Warsaw at Mar 28, 2010 at 9:09 pm
    ** Tags added: mailman3

    --
    Need a 'no-daemonize' option for '/bin/mailman start'
    https://bugs.launchpad.net/bugs/497968
    You received this bug notification because you are a member of Mailman
    Coders, which is subscribed to GNU Mailman.
  • Barry Warsaw at Mar 28, 2010 at 9:42 pm
    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

    --
    Need a 'no-daemonize' option for '/bin/mailman start'
    https://bugs.launchpad.net/bugs/497968
    You received this bug notification because you are a member of Mailman
    Coders, which is subscribed to GNU Mailman.
  • Barry Warsaw at Jun 19, 2010 at 8:49 pm
    ** Changed in: mailman
    Status: Triaged => Won't Fix

    --
    Need a 'no-daemonize' option for '/bin/mailman start'
    https://bugs.launchpad.net/bugs/497968
    You received this bug notification because you are a member of Mailman
    Coders, which is subscribed to GNU Mailman.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-coders @
categoriespython
postedDec 17, '09 at 9:30p
activeJun 19, '10 at 8:49p
posts6
users2
websitelist.org

2 users in discussion

Barry Warsaw: 4 posts Steve Burling: 2 posts

People

Translate

site design / logo © 2022 Grokbase