Need a 'no-daemonize' option for '/bin/mailman start'

Bug #497968 reported by Steve Burling
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Won't Fix
Medium
Unassigned
3.0
Won't Fix
Medium
Unassigned

Bug Description

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.

Tags: mailman3
Revision history for this message
Barry Warsaw (barry) wrote :

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
importance: Undecided → Medium
milestone: none → 3.0.0a5
Revision history for this message
Steve Burling (srb) wrote :

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.

Barry Warsaw (barry)
tags: added: mailman3
Revision history for this message
Barry Warsaw (barry) wrote :

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.

Barry Warsaw (barry)
Changed in mailman:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.