RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 820311 - Manpage: rsyslogd does the fork in debug mode while manpage says otherwise
Summary: Manpage: rsyslogd does the fork in debug mode while manpage says otherwise
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rsyslog
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Heinrich
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
Depends On:
Blocks: 805204
TreeView+ depends on / blocked
 
Reported: 2012-05-09 15:11 UTC by Karel Srot
Modified: 2012-06-20 06:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the manual page stated that the '-d' option which turns on debugging causes the daemon to run in foreground. This was misleading as the current behavior is to run in background. The manual page was updated to reflect the correct behavior.
Clone Of:
Environment:
Last Closed: 2012-06-20 06:59:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0796 0 normal SHIPPED_LIVE Moderate: rsyslog security, bug fix, and enhancement update 2012-06-19 19:29:32 UTC

Description Karel Srot 2012-05-09 15:11:16 UTC 
Description of problem:

rsyslog-5.8.10-1.el6.x86_64

When starting rsyslogd in debug mode (rsyslogd -d) the process should not fork and disconnect from the terminal but it actually does. 
This bug makes rsyslogd debugging hard.

This is a regression introduced by rsyslog update in bug 672182.
Comment 4 Karel Srot 2012-05-10 16:33:45 UTC 
Lowering the severity since this can be workarounded with 
rsyslogd -dn

But anyway it seems to be a bug & regression
Comment 5 Tomas Heinrich 2012-05-11 13:06:48 UTC 
According to upstream, this is the intended behavior.
Comment 6 Karel Srot 2012-05-14 05:49:07 UTC 
Reopening this bug for updating the rsyslogd manpage. 

ATM it states:

       -d     Turns on debug mode.  Using this the daemon will not proceed
              a fork(2) to set  itself in  the  background, but opposite 
              to that stay in the foreground and write much debug 
              information on the current tty.  See the DEBUGGING section 
              for more information.

which is in opposite to #c5 (intended behavior).
Comment 11 Tomas Heinrich 2012-05-17 17:00:59 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the manual page stated that the '-d' option which turns on debugging causes the daemon to run in foreground.
This was misleading as the current behavior is to run in background. The manual page was updated to reflect the correct behavior.
Comment 12 Dalibor Pospíšil 2012-05-18 10:55:30 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1,2 @@
-Previously, the manual page stated that the '-d' option which turns on debugging causes the daemon to run in foreground.
This was misleading as the current behavior is to run in background. The manual page was updated to reflect the correct behavior.+Previously, the manual page stated that the '-d' option which turns on debugging causes the daemon to run in foreground.
+This was misleading as the current behavior is to run in background. The manual page was updated to reflect the correct behavior.
Comment 15 errata-xmlrpc 2012-06-20 06:59:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0796.html
Note You need to log in before you can comment on or make changes to this bug.