Re: [Mailman-Users] Mailman vs OSX vs launchd
I know, I'm reopening a ten month old thread. But I think I have a good workaround. On Fri, 26 Jun 2009, Sebastian Hagedorn wrote: --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 ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (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. I've been playing around with Mailman on a 10.6 (Snow Leopard) machine. It's for testing right now (at the next refresh of Mac Minis or iMacs, I plan to buy one to replace my PPC iMac that is currently my everything server - for now I'm testing on my laptop, the only Intel Mac I currently have). So I found that unlike on the PPC iMac, where Mailman starts OK after about 75% of the boots, on the laptop, it consistently died. No stray process system.log message but perhaps that's a 10.5/10.6 difference. But I did see that the lock files were being created in $mailman_prefix/locks. So what's different? Well, the laptop is a lot faster. Factor? I think so. I know almost nothing about the internals of forking processes and daemonizing but if I have it right, when 'mailmanctl start' is run, it forks a second copy which daemonizes. Meanwhile, the first copy of mailmanctl exits. My guess is that the first copy was exiting and the process terminating before the second copy had performed whatever magic it does to deamonize and run on its own. My workaround, which appears to work so far, is to have launchd, rather than run mailmanctl directly (via a .plist in /Library/LaunchDaemons), instead run a script in root's home directory that runs mailmanctl, then sleeps for one second before exiting: #!/bin/sh /usr/local/mailman/bin/mailmanctl -s start sleep 1 -- Larry Stone lston...@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
Re: [Mailman-Users] Mailman vs OSX vs launchd
Larry Stone wrote: I know almost nothing about the internals of forking processes and daemonizing but if I have it right, when 'mailmanctl start' is run, it forks a second copy which daemonizes. Meanwhile, the first copy of mailmanctl exits. My guess is that the first copy was exiting and the process terminating before the second copy had performed whatever magic it does to deamonize and run on its own. It probably has nothing to do with this, but through Mailman 2.1.13, mailmanctl forks the eventual daemon with file descriptors for stdin, stdout and stderr, possibly attached to the terminal. Normally, the only symptom is if you start Mailman in a terminal session and then log out, the session doesn't completely close until you physically disconnect, but this may have an effect on your situation. I do have an Intel iMac amongst several other machines, but I know essentially nothing about launchd. Anyway, there is a patch to mailmanctl at http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1221 which probably won't make a difference to your case, but might. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
Am/On Fri, 26 Jun 2009 11:06:40 -0500 schrieb/wrote Larry Stone: On Fri, 26 Jun 2009, Sebastian Hagedorn wrote: On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote: If I allow launchd to start it ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds I just caught that Bryan notes that he receives an endless succession of those messages where as I see one and that's it. Comparing our launchd .plist files, I see a few differences: Bryan: keyOnDemand/key false/ Me: keyOnDemand/key true/ keyRunAtLoad/key true/ Larry, you are my hero, thanks! That looks like working :-) 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
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 ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds Known issue, no idea why. I've been running Mailman on Client OS X since the Tiger days. As soon as I upgraded to Leopard, I started seeing this happen intermittently. I have a launchd plist almost identical to yours. It is intermittent for me. Probably happens about 1 in 3 boots. I try to remember to check that it's running after reboots. If not, I have a cron job that runs hourly to check for the proper number of qrunners and send me e-mail if any or all are missing. I have the same issue as Bryan (and my plist looks simular) and find this in my logs, when I start mailman via launchd, if I start it by CLI, I don't see this issue: Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: master qrunner is already running. Jun 26 20:16:29 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: master qrunner is already running. Jun 26 20:16:41 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: master qrunner is already running. Jun 26 20:16:52 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: master qrunner is already running. Jun 26 20:17:03 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: master qrunner is already running. Jun 26 20:17:13 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds But I have this issue always on a 10.5.7 PPC-Server . So what would be the alternative? 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
On 6/26/09 6:22 AM, Matthias Schmidt at 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 ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds Known issue, no idea why. I've been running Mailman on Client OS X since the Tiger days. As soon as I upgraded to Leopard, I started seeing this happen intermittently. I have a launchd plist almost identical to yours. It is intermittent for me. Probably happens about 1 in 3 boots. I try to remember to check that it's running after reboots. If not, I have a cron job that runs hourly to check for the proper number of qrunners and send me e-mail if any or all are missing. I have the same issue as Bryan (and my plist looks simular) and find this in my logs, when I start mailman via launchd, if I start it by CLI, I don't see this issue: Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: master qrunner is already running. Jun 26 20:16:29 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: master qrunner is already running. Jun 26 20:16:41 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: master qrunner is already running. Jun 26 20:16:52 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: master qrunner is already running. Jun 26 20:17:03 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: The master qrunner lock could not be acquired because it appears as if another Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: master qrunner is already running. Jun 26 20:17:13 myMac com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 8 seconds This is not the same issue as Bryan and I have. The log entries you have posted indicate that you are trying to start Mailman twice (the issue Bryan and I have is Mailman dying with the stray process message). Perhaps you have two different launchd scripts that try to to start Mailman. Launchd looks in both /System/Library/LaunchDaemons and /Library/LaunchDaemons. The former is supposed to be for Apple provided scripts with the latter for user/3rd party application scripts. My mailman.plist is in /Library/LaunchDaemons but you should check both and grep for mailmanctl. -- 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 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
--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 ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (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. -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. pgpS9zgP1uR7d.pgp Description: PGP signature -- 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
On Jun 26, 2009, at 7:49 AM, Sebastian Hagedorn wrote: 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. FWIW in MM3, the two functions of mailmanctl have been split into two separate scripts. bin/master is the master queue runner watcher script and it does not daemonize. bin/mailmanctl is simply the control interface to master and it does daemonize. There may not be too much Mailman3-ish about the new scripts so it could be backported (though it probably requires Python 2.6 or possibly 2.5). -Barry PGP.sig Description: This is a digitally signed message part -- 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
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 ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (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
Re: [Mailman-Users] Mailman vs OSX vs launchd
Larry Bryan -- If it helps you at all, I saw the same problems with launchd on my Mailman 2.1.11 install on Mac OS X Server 10.5.5 when we migrated that machine to 10.5 from 10.4. We abandoned launchd in favor of the older /Library/StartupItems/ method and have had no problems since then. I know that we'll have to replace this with launchd at some point, so please keep us informed if you find true solution to the problem. Drew Tenenholz -- 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
On Fri, 26 Jun 2009, Sebastian Hagedorn wrote: On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote: If I allow launchd to start it ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds I just caught that Bryan notes that he receives an endless succession of those messages where as I see one and that's it. Comparing our launchd .plist files, I see a few differences: Bryan: keyOnDemand/key false/ Me: keyOnDemand/key true/ keyRunAtLoad/key true/ Bryan does not have RunAtLoad but the default is false. I think this is why he sees the endless succession and I don't. Wiht RunAtLoad but OnDemand set true, my system tries once at startup and that's it. Bryan, due to OnDemand being false (meaning keep it running continuously), keeps trying. Another difference (but I think making no difference is: Bryan: keyProgram/key string/usr/share/mailman/bin/mailmanctl/string keyProgramArguments/key array stringmailmanctl/string string-s/string stringstart/string /array Me: keyProgramArguments/key array string/Applications/Mailman/bin/mailmanctl/string string-s/string stringstart/string /array I don't have a Program key. I don't think this is relevant as I specify the full path in ProgramArguments which Bryan does not need to do since he specified the path in Program. 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. I'm not so sure. It worked fine for me under Tiger (client). Drew reports the same thing with OS X Server - worked fine under Tiger (10.4.x) and then the same problems as the rest of us with Leopard. Also, I can't say I agree that launchd expects the program to stick around. With it the way I have it set (RunAtLoad true and OnDemand true), it makes one attempt at startup and does not care after that whether it started or not. I'll note that I also have Clam-AV's daemon (clamd) starting the same way and it seems to work OK but some of the technical issues of launching daemon with launchd are beyond me. However, the launchd.plist(5) man page says: EXPECTATIONS Daemons or agents managed by launchd are expected to behave certain ways. A daemon or agent launched by launchd MUST NOT do the following in the process directly launched by launchd: o fork(2) and have the parent process exit(3) or _exit(2). o Call daemon(3) A daemon or agent launched by launchd SHOULD NOT do the following as a part of their startup initialization: Setup the user ID or group ID. o Setup the working directory. o chroot(2) o setsid(2) o Close stray file descriptors. o Change stdio(3) to /dev/null. o Setup resource limits with setrusage(2). o Setup priority with setpriority(2). o Ignore the SIGTERM signal. A daemon or agent launched by launchd SHOULD: o Launch on demand given criteria specified in the XML property list. More information can be found in launch(3). o Catch the SIGTERM signal. I'll leave it to those better into the technical end of things to interpret that relative to what mailmanctl does. -- Larry Stone lston...@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 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
Re: [Mailman-Users] Mailman vs OSX vs launchd
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 I get an endless succession of Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds Known issue, no idea why. I've been running Mailman on Client OS X since the Tiger days. As soon as I upgraded to Leopard, I started seeing this happen intermittently. I have a launchd plist almost identical to yours. It is intermittent for me. Probably happens about 1 in 3 boots. I try to remember to check that it's running after reboots. If not, I have a cron job that runs hourly to check for the proper number of qrunners and send me e-mail if any or all are missing. -- 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 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