CVS: tmda-cgi/htdocs auth.ht,1.3,1.4 auth.html,1.6,1.7 compile.ht,1.7,1.8 compile.html,1.10,1.11 config.ht,1.5,1.6 config.html,1.7,1.8 modes.ht,1.2,1.3 modes.html,1.5,1.6 surprise.ht,1.9,1.10 surprise.html,1.10,1.11
Gre7g Luterman <[email protected]>
| Newsgroups | gmane.mail.spam.tmda.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/tmda/tmda-cgi/htdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv22879
Modified Files:
auth.ht auth.html compile.ht compile.html config.ht
config.html modes.ht modes.html surprise.ht surprise.html
Log Message:
Updated documentation to go with the new configure/make install method.
Index: auth.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/auth.ht,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- auth.ht 1 May 2003 02:42:38 -0000 1.3
+++ auth.ht 4 May 2003 23:46:06 -0000 1.4
@@ -12,7 +12,7 @@
<p>This method authenticates logins against user name & password pairs
stored in a password file (or files). tmda-cgi will look either in the
- file specified by the compile script, or in the default locations for the
+ file specified during compilation, or in the default locations for the
password file, but the file(s) must be readable by the CGI.</p>
<p>If you are running in system-wide mode, the password file can be owned
by root. If you are running in single-user mode, the password file can be
@@ -140,7 +140,7 @@
<tt>vchkpw</tt>.</p>
<p>When specifying this method of authentication, you may need to supply
additional parameters to your checkpassword program. By default,
- <tt>compile</tt> will append <tt>/bin/true</tt> or
+ <tt>configure</tt> will append <tt>/bin/true</tt> or
<tt>/usr/bin/true</tt>, but any program that eventually returns
"0" will do.</p>
Index: auth.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/auth.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- auth.html 4 May 2003 20:04:21 -0000 1.6
+++ auth.html 4 May 2003 23:46:06 -0000 1.7
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 13:25:31 2003 -->
+<!-- Sun May 4 18:44:52 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -82,7 +82,7 @@
<p>This method authenticates logins against user name & password pairs
stored in a password file (or files). tmda-cgi will look either in the
- file specified by the compile script, or in the default locations for the
+ file specified during compilation, or in the default locations for the
password file, but the file(s) must be readable by the CGI.</p>
<p>If you are running in system-wide mode, the password file can be owned
by root. If you are running in single-user mode, the password file can be
@@ -210,7 +210,7 @@
<tt>vchkpw</tt>.</p>
<p>When specifying this method of authentication, you may need to supply
additional parameters to your checkpassword program. By default,
- <tt>compile</tt> will append <tt>/bin/true</tt> or
+ <tt>configure</tt> will append <tt>/bin/true</tt> or
<tt>/usr/bin/true</tt>, but any program that eventually returns
"0" will do.</p>
Index: compile.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/compile.ht,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- compile.ht 4 May 2003 20:04:21 -0000 1.7
+++ compile.ht 4 May 2003 23:46:06 -0000 1.8
@@ -18,20 +18,30 @@
<li>you upgrade tmda-cgi to a more recent version (see UPGRADE file)</li>
</ul>
-<p>Compiling is done with a Python program located in the root of the tmda-cgi
- release called <tt>compile</tt>. Although <tt>compile</tt> may be run with a
- large variety of command line switches (see
- <tt>./compile -h | more</tt>), we find it easiest to run in
- interactive mode. Interactive mode will ask you a series of questions and
- provide "best guess" answers as the defaults. Once you have answered all the
- questions, <tt>compile</tt> will generate an executable and byte-compile the
- Python code.</p>
+<p>Compiling is done with the typical:</p>
+
+<blockquote>
+ <pre># ./configure
+# make
+# make install</pre>
+</blockquote>
+
+<a href="#Running">Running <tt>configure</tt></a><br>
+<a href="#Display"><tt>display</tt> Directory</a><br>
+<a href="#NoSu">Additional no-su Setup</a><p>
+
+<h3><a name="Running"></a>Running <tt>configure</tt></h3>
+
+<p>Although <tt>configure</tt> may be run with a large variety of command line
+ switches (see <tt><nobr>./configure -h | more</nobr></tt>), I think you'll
+ find it far easier to run in interactive mode (by not specifying any
+ options). Interactive mode will ask you a series of questions and provide
+ "best guess" answers as the defaults. Once you have answered all the
+ questions, you'll be all ready to compile and install.</p>
<p>If you do not know the answer to one of the interactive questions, don't
panic. Simply hit control-C and the program will save the responses you have
- given. These will be used as the defaults when you re-run <tt>compile</tt>.
-
-<h3><a name="Running"></a>Running <tt>compile</tt></h3>
+ given. These will be used as the defaults when you re-run <tt>configure</tt>.
<p>Depending on the mode you have chosen, you may need to be logged in as a
specific user when you compile tmda-cgi. Consult the following chart:<p>
@@ -63,17 +73,11 @@
</tr>
</table>
-<p>Compile in interactive mode:</p>
-<blockquote>
- <pre>$ ./compile</pre>
-</blockquote>
-
<p>Information requested in the interactive mode:</p>
<ol>
<li>The location of your Python interpreter</li>
<li>Where to save the CGI</li>
<li>The path to TMDA's root directory</li>
- <li>The path to tmda-cgi's root directory</li>
<li>An optional path or "formula" to find the user <tt>config</tt>
files</li>
<li>The <a href="auth.html">authentication mechanism</a> (file / program /
@@ -81,20 +85,26 @@
<li>The web path from the CGI to the <a href="#Display"><tt>display</tt>
directory</a></li>
<li>Mode</li>
- <li>Unprivileged user to use when writing session data (system-wide mode
- only)</li>
<li><a href="virtual.html">Virtual user stub and parameters</a></li>
<li>Real user to use when someone logs in with a virtual e-mail account</li>
+ <li>Path and prefix to use for temporary, session files</li>
+ <li>How old session files may get before they can be cleaned</li>
+ <li>The odds of cleaning up session files</li>
</ol>
+<p>The <tt>configure</tt> program will provide additional information and
+ its best-guess anwers as defaults. Most of these defaults will probably be
+ just fine for your system, but check them all carefully before hitting
+ return.</p>
+
<h3><a name="Display"></a><tt>display</tt> Directory</h3>
<p>Finally, tmda-cgi requires a variety of visual elements saved in a
- <tt>display</tt> directory (see #7, above). This directory comes with the
+ <tt>display</tt> directory (see #6, above). This directory comes with the
tmda-cgi source and will need to be manually copied or symbolically linked
(make sure your web server is configured to follow links!) into the
appropriate web directory.</p>
-<p>Please note that #7 specifies the relative <i>web path</i> from the CGI to
+<p>Please note that #6 specifies the relative <i>web path</i> from the CGI to
the <tt>display</tt> directory, which may be different than the actual path.
For example:</p>
<table border="0" cellspacing="0" cellpadding="0">
@@ -120,9 +130,9 @@
<p>In the above example, the actual path from the CGI to the display directory
is <tt>../htdocs/display/</tt> but the web path is <tt>../display/</tt>. The
web path (<tt>../display/</tt>) is the one that should be entered in question
- #7.</p>
+ #6.</p>
-<h3>Additional no-su Setup</h3>
+<h3><a name="NoSu"></a>Additional no-su Setup</h3>
<p>If you compile in no-su mode, you will need to change permissions on any
existing pending mail and configuration files so that they can be read by the
Index: compile.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/compile.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- compile.html 4 May 2003 20:04:22 -0000 1.10
+++ compile.html 4 May 2003 23:46:06 -0000 1.11
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 13:25:31 2003 -->
+<!-- Sun May 4 18:35:07 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -99,20 +99,30 @@
<li>you upgrade tmda-cgi to a more recent version (see UPGRADE file)</li>
</ul>
-<p>Compiling is done with a Python program located in the root of the tmda-cgi
- release called <tt>compile</tt>. Although <tt>compile</tt> may be run with a
- large variety of command line switches (see
- <tt>./compile -h | more</tt>), we find it easiest to run in
- interactive mode. Interactive mode will ask you a series of questions and
- provide "best guess" answers as the defaults. Once you have answered all the
- questions, <tt>compile</tt> will generate an executable and byte-compile the
- Python code.</p>
+<p>Compiling is done with the typical:</p>
+
+<blockquote>
+ <pre># ./configure
+# make
+# make install</pre>
+</blockquote>
+
+<a href="#Running">Running <tt>configure</tt></a><br>
+<a href="#Display"><tt>display</tt> Directory</a><br>
+<a href="#NoSu">Additional no-su Setup</a><p>
+
+<h3><a name="Running"></a>Running <tt>configure</tt></h3>
+
+<p>Although <tt>configure</tt> may be run with a large variety of command line
+ switches (see <tt><nobr>./configure -h | more</nobr></tt>), I think you'll
+ find it far easier to run in interactive mode (by not specifying any
+ options). Interactive mode will ask you a series of questions and provide
+ "best guess" answers as the defaults. Once you have answered all the
+ questions, you'll be all ready to compile and install.</p>
<p>If you do not know the answer to one of the interactive questions, don't
panic. Simply hit control-C and the program will save the responses you have
- given. These will be used as the defaults when you re-run <tt>compile</tt>.
-
-<h3><a name="Running"></a>Running <tt>compile</tt></h3>
+ given. These will be used as the defaults when you re-run <tt>configure</tt>.
<p>Depending on the mode you have chosen, you may need to be logged in as a
specific user when you compile tmda-cgi. Consult the following chart:<p>
@@ -144,17 +154,11 @@
</tr>
</table>
-<p>Compile in interactive mode:</p>
-<blockquote>
- <pre>$ ./compile</pre>
-</blockquote>
-
<p>Information requested in the interactive mode:</p>
<ol>
<li>The location of your Python interpreter</li>
<li>Where to save the CGI</li>
<li>The path to TMDA's root directory</li>
- <li>The path to tmda-cgi's root directory</li>
<li>An optional path or "formula" to find the user <tt>config</tt>
files</li>
<li>The <a href="auth.html">authentication mechanism</a> (file / program /
@@ -162,20 +166,26 @@
<li>The web path from the CGI to the <a href="#Display"><tt>display</tt>
directory</a></li>
<li>Mode</li>
- <li>Unprivileged user to use when writing session data (system-wide mode
- only)</li>
<li><a href="virtual.html">Virtual user stub and parameters</a></li>
<li>Real user to use when someone logs in with a virtual e-mail account</li>
+ <li>Path and prefix to use for temporary, session files</li>
+ <li>How old session files may get before they can be cleaned</li>
+ <li>The odds of cleaning up session files</li>
</ol>
+<p>The <tt>configure</tt> program will provide additional information and
+ its best-guess anwers as defaults. Most of these defaults will probably be
+ just fine for your system, but check them all carefully before hitting
+ return.</p>
+
<h3><a name="Display"></a><tt>display</tt> Directory</h3>
<p>Finally, tmda-cgi requires a variety of visual elements saved in a
- <tt>display</tt> directory (see #7, above). This directory comes with the
+ <tt>display</tt> directory (see #6, above). This directory comes with the
tmda-cgi source and will need to be manually copied or symbolically linked
(make sure your web server is configured to follow links!) into the
appropriate web directory.</p>
-<p>Please note that #7 specifies the relative <i>web path</i> from the CGI to
+<p>Please note that #6 specifies the relative <i>web path</i> from the CGI to
the <tt>display</tt> directory, which may be different than the actual path.
For example:</p>
<table border="0" cellspacing="0" cellpadding="0">
@@ -201,9 +211,9 @@
<p>In the above example, the actual path from the CGI to the display directory
is <tt>../htdocs/display/</tt> but the web path is <tt>../display/</tt>. The
web path (<tt>../display/</tt>) is the one that should be entered in question
- #7.</p>
+ #6.</p>
-<h3>Additional no-su Setup</h3>
+<h3><a name="NoSu"></a>Additional no-su Setup</h3>
<p>If you compile in no-su mode, you will need to change permissions on any
existing pending mail and configuration files so that they can be read by the
Index: config.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/config.ht,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- config.ht 29 Apr 2003 04:02:08 -0000 1.5
+++ config.ht 4 May 2003 23:46:06 -0000 1.6
@@ -6,8 +6,8 @@
For technical reasons, no one place could hold them all.</p>
<ul>
<li>Parameters needed before authentication are compiled into the binary
- itself. These parameters are set with the <a
- href="compile.html#Running"><tt>compile</tt></a> program.<p></li>
+ itself. These parameters are set during <a
+ href="compile.html#Running">compilation</a>.<p></li>
<li>Parameters that are needed by TMDA are stored in <a
href="tmdaconfig.html">TMDA configuration files</a>.<p></li>
<li>tmda-cgi defaults are stored in <a
Index: config.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/config.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- config.html 4 May 2003 20:04:22 -0000 1.7
+++ config.html 4 May 2003 23:46:06 -0000 1.8
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 13:25:31 2003 -->
+<!-- Sun May 4 18:44:52 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -99,8 +99,8 @@
For technical reasons, no one place could hold them all.</p>
<ul>
<li>Parameters needed before authentication are compiled into the binary
- itself. These parameters are set with the <a
- href="compile.html#Running"><tt>compile</tt></a> program.<p></li>
+ itself. These parameters are set during <a
+ href="compile.html#Running">compilation</a>.<p></li>
<li>Parameters that are needed by TMDA are stored in <a
href="tmdaconfig.html">TMDA configuration files</a>.<p></li>
<li>tmda-cgi defaults are stored in <a
Index: modes.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/modes.ht,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- modes.ht 4 May 2003 20:04:23 -0000 1.2
+++ modes.ht 4 May 2003 23:46:06 -0000 1.3
@@ -45,11 +45,11 @@
who compiled it and therefore cannot access anyone else's personal data.</p>
<p>If multiple users wish to install tmda-cgi in single-user mode (strange, but
- not absurd) then each user can use <tt>compile</tt> to create a different 14k
- shell that launches the Python code. This method is less convenient than the
- system-wide installation (since each user must compile their own copy of
- tmda-cgi and then surf a different URL to access the system), but it is the
- best solution for:</p>
+ not absurd) then each user can use <tt>configure/make</tt> to create a
+ different 14k shell that launches the Python code. This method is less
+ convenient than the system-wide installation (since each user must compile
+ their own copy of tmda-cgi and then surf a different URL to access the
+ system), but it is the best solution for:</p>
<ul>
<li>users without root access to their server<p></li>
Index: modes.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/modes.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- modes.html 4 May 2003 20:04:23 -0000 1.5
+++ modes.html 4 May 2003 23:46:06 -0000 1.6
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 13:25:32 2003 -->
+<!-- Sun May 4 18:44:52 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -126,11 +126,11 @@
who compiled it and therefore cannot access anyone else's personal data.</p>
<p>If multiple users wish to install tmda-cgi in single-user mode (strange, but
- not absurd) then each user can use <tt>compile</tt> to create a different 14k
- shell that launches the Python code. This method is less convenient than the
- system-wide installation (since each user must compile their own copy of
- tmda-cgi and then surf a different URL to access the system), but it is the
- best solution for:</p>
+ not absurd) then each user can use <tt>configure/make</tt> to create a
+ different 14k shell that launches the Python code. This method is less
+ convenient than the system-wide installation (since each user must compile
+ their own copy of tmda-cgi and then surf a different URL to access the
+ system), but it is the best solution for:</p>
<ul>
<li>users without root access to their server<p></li>
Index: surprise.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/surprise.ht,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- surprise.ht 4 May 2003 20:04:24 -0000 1.9
+++ surprise.ht 4 May 2003 23:46:06 -0000 1.10
@@ -11,8 +11,6 @@
<a href="#Authentication">Authentication Ailments</a><br>
<a href="#Attach">Attachment Anxiety</a><br>
<a href="#WhiteBlack">Whitelist, Blacklist... where are the options?</a><br>
-<a href="#RPM">Where, oh where, did the RPM install?</a><br>
-<a href="#Port">Any FreeBSD port in a storm</a><br>
<a href="#Base">Bad Base</a><br>
<a href="#Install">Install Again?</a></p>
@@ -35,11 +33,11 @@
<p>If tmda-cgi tries to run using the wrong version of Python, then you
must specify the correct version at compile time. Instead of typing:</p>
<blockquote>
- <pre>$ ./compile <options></pre>
+ <pre># ./configure <options></pre>
</blockquote>
<p>Type:</p>
<blockquote>
- <pre>$ /usr/bin/python2 compile <options></pre>
+ <pre># /usr/bin/python2 configure <options></pre>
</blockquote>
<p>(Assuming that your Python 2.1+ can be found at
<tt>/usr/bin/python2</tt>.) The compiler will save the correct version of
@@ -108,26 +106,6 @@
href="/config-vars.html#PENDING_BLACKLIST_APPEND"><tt>PENDING_BLACKLIST_APPEND</tt></a>.
The radio buttons and option buttons should appear on the pending list and
pending e-mail viewer once you do.</p>
-
-<h3><a name="RPM"></a>Where, oh where, did the RPM install?</h3>
-<p><tt>./compile</tt> wants to know where I installed TMDA, but I used the RPM,
- and have no idea where it put the files!</p>
-<p>The RPM puts TMDA files all over the place, so when <tt>./compile</tt> asks,
- "Path to TMDA root directory", try:</p>
-<blockquote>
- <code>/usr/lib/python2.2/site-packages</code>
-</blockquote>
-and see if that makes it happy.
-
-<h3><a name="Port"></a>Any FreeBSD port in a storm</h3>
-<p><tt>./compile</tt> wants to know where I installed TMDA, but I used the
- FreeBSD port, and have no idea where it put the files!</p>
-<p>The ports collection puts TMDA files all over the place, so when
- <tt>./compile</tt> asks, "Path to TMDA root directory", try:</p>
-<blockquote>
- <code>/usr/local/lib/python2.2/site-packages</code>
-</blockquote>
-and see if that makes it happy.
<h3><a name="Base"></a>Bad Base</h3>
<p>My <tt>skel</tt> files use <tt>%(Base)s/bin/</tt> to refer to TMDA's
Index: surprise.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/surprise.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- surprise.html 4 May 2003 20:04:24 -0000 1.10
+++ surprise.html 4 May 2003 23:46:06 -0000 1.11
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 13:25:33 2003 -->
+<!-- Sun May 4 18:44:52 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -89,8 +89,6 @@
<a href="#Authentication">Authentication Ailments</a><br>
<a href="#Attach">Attachment Anxiety</a><br>
<a href="#WhiteBlack">Whitelist, Blacklist... where are the options?</a><br>
-<a href="#RPM">Where, oh where, did the RPM install?</a><br>
-<a href="#Port">Any FreeBSD port in a storm</a><br>
<a href="#Base">Bad Base</a><br>
<a href="#Install">Install Again?</a></p>
@@ -113,11 +111,11 @@
<p>If tmda-cgi tries to run using the wrong version of Python, then you
must specify the correct version at compile time. Instead of typing:</p>
<blockquote>
- <pre>$ ./compile <options></pre>
+ <pre># ./configure <options></pre>
</blockquote>
<p>Type:</p>
<blockquote>
- <pre>$ /usr/bin/python2 compile <options></pre>
+ <pre># /usr/bin/python2 configure <options></pre>
</blockquote>
<p>(Assuming that your Python 2.1+ can be found at
<tt>/usr/bin/python2</tt>.) The compiler will save the correct version of
@@ -186,26 +184,6 @@
href="/config-vars.html#PENDING_BLACKLIST_APPEND"><tt>PENDING_BLACKLIST_APPEND</tt></a>.
The radio buttons and option buttons should appear on the pending list and
pending e-mail viewer once you do.</p>
-
-<h3><a name="RPM"></a>Where, oh where, did the RPM install?</h3>
-<p><tt>./compile</tt> wants to know where I installed TMDA, but I used the RPM,
- and have no idea where it put the files!</p>
-<p>The RPM puts TMDA files all over the place, so when <tt>./compile</tt> asks,
- "Path to TMDA root directory", try:</p>
-<blockquote>
- <code>/usr/lib/python2.2/site-packages</code>
-</blockquote>
-and see if that makes it happy.
-
-<h3><a name="Port"></a>Any FreeBSD port in a storm</h3>
-<p><tt>./compile</tt> wants to know where I installed TMDA, but I used the
- FreeBSD port, and have no idea where it put the files!</p>
-<p>The ports collection puts TMDA files all over the place, so when
- <tt>./compile</tt> asks, "Path to TMDA root directory", try:</p>
-<blockquote>
- <code>/usr/local/lib/python2.2/site-packages</code>
-</blockquote>
-and see if that makes it happy.
<h3><a name="Base"></a>Bad Base</h3>
<p>My <tt>skel</tt> files use <tt>%(Base)s/bin/</tt> to refer to TMDA's
_______________________________________
tmda-cvs mailing list
http://tmda.net/lists/listinfo/tmda-cvs