[Qvcs-CVS] qvcs-guide qvcs-guide.xml,1.10,1.11

[<gr...@us...>]

Update of /cvsroot/qvcs-guide/qvcs-guide
In directory sc8-pr-cvs1:/tmp/cvs-serv4694

Modified Files:
	qvcs-guide.xml 
Log Message:
Prepping for the release.  


Index: qvcs-guide.xml
===================================================================
RCS file: /cvsroot/qvcs-guide/qvcs-guide/qvcs-guide.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** qvcs-guide.xml	11 Jul 2003 21:29:26 -0000	1.10
--- qvcs-guide.xml	23 Aug 2003 03:36:48 -0000	1.11
***************
*** 25,31 ****
        </author>
      </authorgroup>
!     <edition>&rhl; 9 Edition</edition>
!     <pubdate>July 11, 2003</pubdate>
!     <releaseinfo>Version: 1.9.1</releaseinfo>
      <copyright>
        <year>2001-2003</year>
--- 25,31 ----
        </author>
      </authorgroup>
!     <edition>&rhl; &ver; Edition</edition>
!     <pubdate>August 22, 2003</pubdate>
!     <releaseinfo>Version: 2.0</releaseinfo>
      <copyright>
        <year>2001-2003</year>
***************
*** 657,660 ****
--- 657,673 ----
      </sect1>
      <sect1>
+       <title>What's in the name?</title>
+       <para>
+         It is useful to check whether the qmail installer set your
+         hostname correctly. Go into
+         <filename>/etc/qmail/control</filename> and check what the
+         file &quot;<filename>me</filename>&quot; says. It may be
+         empty, or it may contain the FQDN of your server. You want to
+         put the official name of your server in that file,
+         e.g. &quot;mail.yourisp.com&quot; -- it should not remain
+         empty, as that will cause some outgoing mail to bounce.
+       </para>
+     </sect1>
+     <sect1>
        <title>Reboot</title>
        <para>
***************
*** 831,841 ****
        <para>
          If you feel edgy about having an automated updater tool
!         running on your system, you may leave yum disabled, but then
!         please subscribe to the redhat errata notification list, so
!         you know when updates are being released. Don't let your server
!         become an internet statistic.
        </para>
        <para>
!         To update a system manually, run:
        </para>
        <programlisting>
--- 844,863 ----
        <para>
          If you feel edgy about having an automated updater tool
!         running on your system, you may leave auto-updating disabled,
!         but then I would suggest putting a &quot;yum
!         check-update&quot; run into your nightly cron run. The
!         following will notify the root user whenever there are updates
!         available for the system:
        </para>
+       <programlisting>
+ &prompt; <userinput>echo "yum -d 0 check-update" > /etc/cron.daily/yum-check.cron</userinput>
+ &prompt; <userinput>chmod a+x /etc/cron.daily/yum-check.cron</userinput>
+       </programlisting>
        <para>
!         Evaluate any updates and apply them. Don't let your server
!         become a part of the sad Internet cracking statistic.
!       </para>
!       <para>
!         To update your system manually, run:
        </para>
        <programlisting>
***************
*** 1483,1486 ****
--- 1505,1539 ----
            false-positives, meaning that you can lose important email.
          </para>
+         <note>
+           <title>Speed things up</title>
+           <para>
+             This little edit will let you speed things up
+             significantly in SpamAssassin. &rhl; &ver; uses Unicode
+             internally, but many Perl programs do not expect to
+             encounter it, and therefore take a LONG time to perform
+             certain queries, such as string matches. To speed things
+             up, it is useful to tell SpamAssassin to always use
+             &quot;en_US&quot; encoding when doing regex matching of
+             strings. Open
+             <filename>/etc/init.d/spamassassin</filename> in your
+             editor, and add one extra line right after the PATH
+             definition:
+           </para>
+           <programlisting>
+ ...
+ [ -f /usr/bin/spamd -o -f /usr/local/bin/spamd ] || exit 0
+ PATH=$PATH:/usr/bin:/usr/local/bin
+ <userinput>LANG=en_US</userinput>
+ 
+ # See how we were called.
+ ...
+           </programlisting>
+           <para>
+             Save and restart spamassassin by issuing
+             &quot;<command>service spamassassin
+             restart</command>.&quot; This should speed things up
+             significantly.
+           </para>
+         </note>
        </sect2>
        <sect2>
***************
*** 1562,1570 ****
        <title>Report your success</title>
        <para>
!         If you found this Guide useful, please let me know by executing:
        </para>
        <programlisting>
! &prompt; <userinput>uname -a | mail qvc...@mr... -s 'Thanks'</userinput>
        </programlisting>
      </sect1>
    </chapter>
--- 1615,1634 ----
        <title>Report your success</title>
        <para>
!         If you found this Guide useful, please let me know by sending
!         this brief email (replacing {your locality} with the name of
!         your town, state, country).
        </para>
        <programlisting>
! &prompt; <userinput>echo "Greetings from {your locality}!" | mail qvc...@mr... -s "Thanks"</userinput>
        </programlisting>
+       <para>
+         Please also consider expressing your gratitude by sending me a
+         gift from my Amazon Wishlist, which you may find on the main
+         website. This will help me leverage the time I put into
+         maintaining this guide and the packages that come with
+         it. After all, this software isn't free as in beer, but free
+         as in &quot;you are free to reward the author
+         accordingly.&quot; :)
+       </para>
      </sect1>
    </chapter>