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

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


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

Modified:
   trunk/openvas-compendium/openvas-compendium.tex
Log:
Fixed extra whitespaces left by slopping editing on my 
part in "Performing a synchronization with an OpenVAS NVT Feed".



Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex	2009-05-07 08:33:37 UTC (rev 3270)
+++ trunk/openvas-compendium/openvas-compendium.tex	2009-05-07 08:52:37 UTC (rev 3271)
@@ -822,7 +822,7 @@
 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 repository 
+(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.
@@ -837,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