Misleading info in rsyslogd man page
Issue
- Some misleading info in rsyslogd man page.
HUP This lets rsyslogd 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 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.
- In the above paragraph, it is written that
Future versions will remove this restart functionality of HUP (it will go away in v5). But v5 is already running in RHEL6. - Correct behaviour of
rsyslogdshould be written in the above paragraph.
Environment
- Red Hat Enterprise Linux 6
- Rsyslog v5
- Rsyslog v7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
