[Bug 356961] Consider building with --with-xft=all
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=356961
Fedora Admin XMLRPC Client <fedora-admin-xmlrpc(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|ville.skytta(a)iki.fi |loganjerry(a)gmail.com
--- Comment #5 from Fedora Admin XMLRPC Client <fedora-admin-xmlrpc(a)redhat.com> 2009-06-15 14:00:22 EDT ---
This package has changed ownership in the Fedora Package Database. Reassigning
to the new owner of this component.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years
[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=136141
--- Comment #34 from Tomas Heinrich <theinric(a)redhat.com> 2009-06-15 09:35:46 EDT ---
I'm not sure whether this is the right solution.
Printing all the syntax errors from the init script can be pretty
ugly. Maybe it would be better to just detect errors and issue one big
red warning that you should check your configuration.
What's worse is that rsyslog will keep spamming the console after
startup.
Regarding the other reasons that can prevent rsyslog from running,
obviously the daemon will not start, which is the first clue that
something is wrong, and the init script will issue a failure
notification. Then it's up to you to investigate.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years
[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=136141
--- Comment #31 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-06-15 02:04:04 EDT ---
> It does _not_ log them. At least not in the example I offer in this ticket.
> Yes, it's bad luck that an entire rule gets disabled, see comment 14, please.
You almost seem to intentionally misunderstand me. Look at the code, or do a
*.* /path/to/file
in your rsyslog.conf and you will see that rsyslog *does* log these messages.
But no point in further arguing this...
I made a test with stderr. I changed rsyslogd so that it keeps fd 2 open after
a fork. Then I did
/sbin/service rsyslog start
Nothing showed up on the terminal. Just to make sure, I added an
fprintf(stderr, "rsyslogd start\n");
right as the first line of main(). Again, I did a
/sbin/service rsyslog start
And again, nothing showed up at the controlling terminal. My conclusion is that
/sbin/service does suppress the daemon's stderr. Am I wrong here? What kind of
magic do I need to do to make stderr appear?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years