[Openvas-commits] r3270 - trunk/openvas-compendium

scm-commit@wald.intevation.org scm-commit at wald.intevation.org
Thu May 7 10:33:38 CEST 2009


Author: geoff
Date: 2009-05-07 10:33:37 +0200 (Thu, 07 May 2009)
New Revision: 3270

Modified:
   trunk/openvas-compendium/ChangeLog
   trunk/openvas-compendium/openvas-compendium.tex
Log:
openvas-compendium.tex: Edited "Performaing a synchronization 
with an OpenVAS NVT Feed" section for grammar and flow.



Modified: trunk/openvas-compendium/ChangeLog
===================================================================
--- trunk/openvas-compendium/ChangeLog	2009-05-07 08:05:10 UTC (rev 3269)
+++ trunk/openvas-compendium/ChangeLog	2009-05-07 08:33:37 UTC (rev 3270)
@@ -1,3 +1,8 @@
+2009-05-07 Geoff Galitz <geoff at galitz.org>
+
+	* openvas-compendium.tex: Edited "Performaing a synchronization
+	with an OpenVAS NVT Feed" section for grammar and flow.
+
 2009-05-06 Geoff Galitz <geoff at galitz.org>
 
 	* openvas-compendium.tex: Edited "Choose Location of Scan-Server"

Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex	2009-05-07 08:05:10 UTC (rev 3269)
+++ trunk/openvas-compendium/openvas-compendium.tex	2009-05-07 08:33:37 UTC (rev 3270)
@@ -786,9 +786,8 @@
 files) which can be downloaded into your OpenVAS server installation.
 
 In fact, only changed and new NVTs will be downloaded along with their signature
-files (``.asc'') and an overall ``md5sums''. This synchronization process uses
-the RSYNC technology. The signatures are only relevant for you if you configure
-your OpenVAS server to execute only trusted NVTs.
+files (``.asc'') and ``md5sums''. This synchronization process uses
+the RSYNC technology. The signatures are only relevant for trusted NVTs.
 
 \xname{prerequisites-server}
 \subsection{Prerequisites}
@@ -797,39 +796,38 @@
 ``openvas-nvt-sync'' script, you need to have the standard \verb|rsync| and
 \verb|md5sum| tools available on the system where your OpenVAS server instance
 is running. If you installed OpenVAS from a binary package, the package
-management of your distribution should have taken care to meet these
-dependencies already.
+manager for your distribution should have taken of these dependencies already.
 
 \xname{synchronizing-with-openvas-nvt-feed}
 \subsection{Performing a synchronization with an OpenVAS NVT Feed}
 
-To synchronize your NVT repository with an OpenVAS NVT Feed, you need to follow
+To synchronize your NVT repository with an OpenVAS NVT Feed, follow
 these steps:
 
 \begin{enumerate}
- \item Check the configuration of the synchronization command:
+ \item Check the configuration of the synchronization script:
 Usually you will find this shell script installed as
 \verb|/usr/sbin/openvas-nvt-sync|.
 
 You should verify that the variables ``NVT\_DIR'' and ``FEED'' are correct. This
 should be the case for NVT\_DIR if you did not deviate from the standard build
 and install routine. For FEED there is currently only the pre-configured one
-available anyway. So, just don't change it.
+anyway. So, just don't change it.
 
 \item Run the synchronization command:
 \begin{verbatim}
            # openvas-nvt-sync
 \end{verbatim}
 
-It will connect to the currently only available NVT feed. At the end, it will
+It will connect to the currently available NVT feed. At the end, it will
 verify the md5 checksums of all synchronized files. If any of them fails, an
 error is reported. In this case you should retry a couple of minutes later
-(reasons for failures could be network lags or that the feed was updated at the 
-same time).
+(reasons for failures could be network lags or that the feed repository 
+was being updated at the time).
 If the problem occurs again, please report it to the OpenVAS discussion
 mailing list.
-If you want to automatically update you NVT collection, you can a description of
-the required steps in chapter \ref{sec:autosync}.
+If you want to automatically update your NVT collection, follow the steps
+in chapter \ref{sec:autosync}.
 
 \item Restart the OpenVAS server (openvasd):
 \begin{verbatim}
@@ -839,7 +837,7 @@
 Where PID is the process ID of the main openvasd. You may see in the
 ``openvas-nvt-sync'' script how this should work ideally, but currently it does
 not work. You might consider using the ``killall openvasd'' command if you
-really know what this means.
+really know what this means. 
 \end{enumerate}
 
 \xname{available-nvt-feed-services}



More information about the Openvas-commits mailing list