removed mentioning HUP as a way of restarting from the doc set

... part of the deprecation effort for v5

doc/index.html

@@ -25,8 +25,7 @@ To do the really cool things, though,
 you need to learn a bit about its new features.
 The man pages offer a bare minimum of information (and are still quite long). Read the 
 <a href="manual.html">html documentation</a> instead.
-When you change the configuration,
-remember to restart (or HUP) rsyslogd, because otherwise it won't use your
-new settings (and you'll end up totally puzzled why this great config of yours
-does not even work a bit...;))
+When you change the configuration, remember to restart rsyslogd, because otherwise
+it will not use your new settings (and you'll end up totally puzzled why this great
+config of yours does not even work a bit...;))
 </body></html>

doc/manual.html

@@ -41,7 +41,6 @@ the links below for the</b><br></p><ul>
 <li><a href="generic_design.html">backgrounder on
 generic syslog application design</a><!-- not good as it currently is ;) <li><a href="contributors.html">contributor &quot;Hall of Fame&quot;</a>--></li>
 <li><a href="modules.html">description of rsyslog modules</a></li>
-<li><a href="man_rsyslogd.html">rsyslogd man page</a> (heavily outdated)</li>
 </ul>
 <p><b>We have some in-depth papers on</b></p>
 <ul>

doc/rsconf1_dirgroup.html

@@ -7,7 +7,7 @@
 <p><b>Type:</b> global configuration directive</p>
 <p><b>Default:</b> </p>
 <p><b>Description:</b></p>
-<p>Set the group for directories newly created. Please note that this setting does not affect the group of directories already existing. The parameter is a group name, for which the groupid is obtained by rsyslogd on startup and on HUPing. Interim changes to the user mapping are not detected.</p>
+<p>Set the group for directories newly created. Please note that this setting does not affect the group of directories already existing. The parameter is a group name, for which the groupid is obtained by rsyslogd on during startup processing. Interim changes to the user mapping are not detected.</p>
 <p><b>Sample:</b></p>
 <p><code><b>$DirGroup loggroup</b></code></p>
 

doc/rsconf1_dirowner.html

@@ -7,7 +7,7 @@
 <p><b>Type:</b> global configuration directive</p>
 <p><b>Default:</b> </p>
 <p><b>Description:</b></p>
-<p>Set the file owner for directories newly created. Please note that this setting does not affect the owner of directories already existing. The parameter is a user name, for which the userid is obtained by rsyslogd on startup and on HUPing. Interim changes to the user mapping are not detected.</p>
+<p>Set the file owner for directories newly created. Please note that this setting does not affect the owner of directories already existing. The parameter is a user name, for which the userid is obtained by rsyslogd during startup processing. Interim changes to the user mapping are not detected.</p>
 <p><b>Sample:</b></p>
 <p><code><b>$DirOwner loguser</b></code></p>
 

doc/rsconf1_filegroup.html

@@ -7,7 +7,7 @@
 <p><b>Type:</b> global configuration directive</p>
 <p><b>Default:</b> </p>
 <p><b>Description:</b></p>
-<p>Set the group for dynaFiles newly created. Please note that this setting does not affect the group of files already existing. The parameter is a group name, for which the groupid is obtained by rsyslogd on startup and on HUPing. Interim changes to the user mapping are not detected.</p>
+<p>Set the group for dynaFiles newly created. Please note that this setting does not affect the group of files already existing. The parameter is a group name, for which the groupid is obtained by rsyslogd during startup processing. Interim changes to the user mapping are not detected.</p>
 <p><b>Sample:</b></p>
 <p><code><b>$FileGroup loggroup</b></code></p>
 

doc/rsconf1_fileowner.html

@@ -7,7 +7,7 @@
 <p><b>Type:</b> global configuration directive</p>
 <p><b>Default:</b> </p>
 <p><b>Description:</b></p>
-<p>Set the file owner for dynaFiles newly created. Please note that this setting does not affect the owner of files already existing. The parameter is a user name, for which the userid is obtained by rsyslogd on startup and on HUPing. Interim changes to the user mapping are not detected.</p>
+<p>Set the file owner for dynaFiles newly created. Please note that this setting does not affect the owner of files already existing. The parameter is a user name, for which the userid is obtained by rsyslogd during startup processing. Interim changes to the user mapping are not detected.</p>
 <p><b>Sample:</b></p>
 <p><code><b>$FileOwner loguser</b></code></p>
 

doc/rsyslog_php_syslog_ng.html

@@ -107,7 +107,7 @@ server machine, "syslog" is the database name (default from the schema
 and "pass" are the logon credentials. Use a user with low privileges, insert into the 
 logs table is sufficient. "syslog-ng" is the template name and tells rsyslogd to 
 use the SQL statement shown above.</p>
-<p>Once you have made the changes, all you need to do is reload (or HUP) 
+<p>Once you have made the changes, all you need to do is restart
 rsyslogd. Then, you should see syslog messages flow into your database - and 
 show up in php-syslog-ng.</p>
 <h2>Conclusion</h2>

doc/rsyslog_recording_pri.html

@@ -62,7 +62,7 @@ semicolon:</p>
 <p>That's all you need to do. There is one common pitfall: you need to define 
 the template before you use it in a selector line. Otherwise, you will receive 
 an error.</p>
-<p>Once you have applied the changes, you need to restart or HUP rsyslogd. It 
+<p>Once you have applied the changes, you need to restart rsyslogd. It 
 will then pick the new configuration.</p>
 <h2>What if I do not want rsyslogd to be the standard syslogd?</h2>
 <p>If you do not want to switch to rsyslog, you can still use it as a setup aid. 

doc/rsyslog_tls.html

@@ -127,7 +127,7 @@ This is all you need to do. You can use the rest of your rsyslog.conf
 together with this configuration. The way messages are received does
 not interfer with any other option, so you are able to do anything else
 you like without any restrictions.
-<p>Restart (or HUP) rsyslogd. The server should now be fully
+<p>Restart rsyslogd. The server should now be fully
 operational.</p>
 <h3>Client Setup</h3>
 <p>The client setup is equally&nbsp;simple. You need less

tools/rsyslogd.8

@@ -248,20 +248,17 @@ kill -HUP $(cat /var/run/rsyslogd.pid)
 .B HUP
 This lets
 .B rsyslogd
-perform a re-initialization.  All open files are closed, the
-configuration file (default is 
-.IR /etc/rsyslog.conf ")"
-will be reread and the
-.BR rsyslog (3)
-facility is started again.
+perform close all open files.
+Also, in v3 a full restart will be done in order to read changed configuration files.
 Note that this means a full rsyslogd restart is done. This has, among others,
 the consequence that TCP and other connections are torn down. Also, if any
 queues are not running in disk assisted mode or are not set to persist data
 on shutdown, queue data is lost. HUPing rsyslogd is an extremely expensive
 operation and should only be done when actually necessary. Actually, it is
-a rsyslgod stop immediately followed by a restart. Future versions will probably
-include a special handling which only closes files, but will not cause any
-of the other effects.
+a rsyslgod stop immediately followed by a restart. Future versions will remove
+this restart functionality of HUP (it will go away in v5). So it is advised to use
+HUP only for closing files, and a "real restart" (e.g. /etc/rc.d/rsyslogd restart)
+to activate configuration changes.
 .TP
 .B TERM ", " INT ", " QUIT
 .B Rsyslogd