confdroid/confdroid_clamav
1
0
Fork 0
Code Issues Wiki Activity

recommit for updates in build 45

Browse Source
This commit is contained in:
Jenkins ConfDroid
2021-09-10 13:57:29 +02:00
parent fd307d5a14
commit aeca6700e2
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/file.README.html
View File

@@ -75,13 +75,13 @@ and configurations.</p>
<h2 id="label-WARNING">WARNING</h2> <h2 id="label-WARNING">WARNING</h2>
<p><code>**__!!! Attention: Never use this puppet module on systems which have <p><strong><em>Attention: Never use this puppet module on systems which have
been previously configured manually. It is impossible to predict how and been previously configured manually. It is impossible to predict how and
what would have been configured, hence previous configurations outside the what would have been configured, hence previous configurations outside the
scope of this module may be overwritten! Automated configurations require a scope of this module may be overwritten! Automated configurations require a
test environment to verify that the module suits the purpose intended by test environment to verify that the module suits the purpose intended by
the user, as well as tune the parameters, before deploying into live the user, as well as tune the parameters, before deploying into live
production!!! __**</code></p> production</em></strong></p>
<h2 id="label-Dependencies">Dependencies</h2> <h2 id="label-Dependencies">Dependencies</h2>

4
doc/index.html
View File

@@ -75,13 +75,13 @@ and configurations.</p>
<h2 id="label-WARNING">WARNING</h2> <h2 id="label-WARNING">WARNING</h2>
<p><code>**__!!! Attention: Never use this puppet module on systems which have <p><strong><em>Attention: Never use this puppet module on systems which have
been previously configured manually. It is impossible to predict how and been previously configured manually. It is impossible to predict how and
what would have been configured, hence previous configurations outside the what would have been configured, hence previous configurations outside the
scope of this module may be overwritten! Automated configurations require a scope of this module may be overwritten! Automated configurations require a
test environment to verify that the module suits the purpose intended by test environment to verify that the module suits the purpose intended by
the user, as well as tune the parameters, before deploying into live the user, as well as tune the parameters, before deploying into live
production!!! __**</code></p> production</em></strong></p>
<h2 id="label-Dependencies">Dependencies</h2> <h2 id="label-Dependencies">Dependencies</h2>