Steve,
I was hoping to be polite and avoid the "why is Mailman inflicting
this antiquated utility on me?" implication. ;)
You have explained why I've no other such errors - there are no other
crons on any of my servers. All my customizations are done via launchd.
I'd be very grateful if you'd like to share your launchd.plist
efforts. Replacing Mailman's crons went on my list as soon as I
understood what was happening. It'd be a pleasure to eliminate the
crons, since they strike me as inelegant by comparison.
Thanks,
Bryan
To which I reply:
This is because Apple has deprecated cron, and really wants you to
use launchd instead. You'll see one of those messages for
*everything* that cron runs -- you're just seeing the common ones
because they run so often.
I've written a bunch of launchd.plist files for all the various
Mailman cron jobs; if you want them, let me know.
--
Steve Burling
<mailto:s...@umich.edu>
University of Michigan, ICPSR Voice: +1 734
615.3779
330 Packard Street FAX: +1 734
647.8700
Ann Arbor, MI 48104-2910
------------------------------------------------------
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