From 7fd3afbe2480275fe41fa0169ed72abd1f425048 Mon Sep 17 00:00:00 2001
From: bwarsaw <>
Date: Tue, 14 Dec 2004 04:27:49 +0000
Subject: Committing lots of documentation updates, including linking up to the
new mailman-installation guide, and filling out the other formats that seemed
to be missing.
---
admin/www/mailman-install/node40.html | 131 ++++++++++++++++++++++++++++++++++
1 file changed, 131 insertions(+)
create mode 100644 admin/www/mailman-install/node40.html
(limited to 'admin/www/mailman-install/node40.html')
diff --git a/admin/www/mailman-install/node40.html b/admin/www/mailman-install/node40.html
new file mode 100644
index 00000000..54352cce
--- /dev/null
+++ b/admin/www/mailman-install/node40.html
@@ -0,0 +1,131 @@
+
+
+
+
+
+
+
+
+
+
+
+
+8 Set up cron
+
+
+
+Several Mailman features occur on a regular schedule, so you must set up
+cron to run the right programs at the right time5.
+
+
+If your version of crontab supports the -u option, you must be
+root to do this next step. Add $prefix/cron/crontab.in as a
+crontab entry by executing these commands:
+
+
+If you used the --with-username option, use that user name
+instead of mailman for the -u argument value. If your
+crontab does not support the -u option, try these commands:
+
+
+
+ % cd $prefix/cron
+ % su - mailman
+ % crontab crontab.in
+
Note that
+if you're upgrading from a previous version of Mailman, you'll want to install
+the new crontab, but be careful if you're running multiple Mailman
+installations on your site! Changing the crontab could mess with other
+parallel Mailman installations.
+
+
