Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

rsyslog no longer creating new log files immediately after SIGHUP

Solution Verified - Updated 2016-01-18T18:52:47+00:00 -

Issue

After updating to rsyslog version 5, new log files are not created immediately after sending rsyslogd a HUP signal (for example, after the log files are moved by logrotate or a custom rotate script).
- Previous versions of rsyslog created empty files immediately after receipt of SIGHUP.
- Note: The expected behaviour is observed when doing a full restart: empty files are created.

Environment

Red Hat Enterprise Linux 6
- rsyslog >= rsyslog-5.8.10-2.el6
Red Hat Enterprise Linux 5
- rsyslog >= rsyslog5-5.8.12-4.el5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)