[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 #12 from Tomas Heinrich <theinric(a)redhat.com> 2009-05-20 09:21:54 EDT ---
I'm not sure what you mean by DoS;
If there's a typo in a rule definition, that rule is disabled and a warning is
issued where possible. All other valid rules still work.
After making changes to the configuration file, you have a way to verify they
are correct.
It might be possible to always run 'rsyslog -N -f <cfg>' from the init script
before starting rsyslog, but I'm not sure if this is the right solution. Are
you ok with this?
--
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.
14 years, 11 months
[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
Michael Schwendt <bugs.michael(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |ASSIGNED
Version|9 |10
Resolution|NOTABUG |
--- Comment #11 from Michael Schwendt <bugs.michael(a)gmx.net> 2009-05-19 15:06:49 EDT ---
The original steps to reproduce it are still valid.
$ rpm -q rsyslog
rsyslog-3.21.10-2.fc10.i386
A simple typo -- as in the example in the original bug report -- results in
DoS. With rsyslog.
--
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.
14 years, 11 months
[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
Tomas Heinrich <theinric(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |NOTABUG
--- Comment #10 from Tomas Heinrich <theinric(a)redhat.com> 2009-05-19 09:01:44 EDT ---
When rsyslog encounters an error in the configuration file, it generates
a message with syslog.error priority, which can be logged elsewhere.
When running in debug mode, it also writes the message to stderr.
Since version 3.21.1 rsyslog supports a command line option (-N) to validate
the configuration file.
--
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.
14 years, 11 months
[Bug 199812] ACPI: Unable to turn cooling device [ffff81007ffa6810] 'on' is spewed repeatedly on the console
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=199812
--- Comment #27 from John Guthrie <guthrie(a)counterexample.org> 2009-05-14 04:14:58 EDT ---
(In reply to comment #25)
> Output of acpitool on my system exhibiting the behavior:
>
> # acpitool -t
> Thermal zone 1 : passi, 65 C
> Trip points :
> -------------
> critical (S5): 200 C
> passive: 50 C: tc1=4 tc2=3 tsp=60 devices=0xffff8800012372b0
> active[0]: 50 C: devices=0xffff880000f7b990
Here is the output on my system:
leibniz_1008% acpitool -t
Thermal zone 1 : passi, 39 C
Trip points :
-------------
critical (S5): 100 C
passive: -248 C: tc1=4 tc2=3 tsp=60 devices=CPU0
active[0]: -266 C: devices= FAN
Note the temperatures that are approaching absolute zero.
One fix that was given all the way back in the URL in comment #7 seemed to
indicate that at one time, you could simply echo trip points that were more
sane into /proc/acpi/thermal_zone/THRM/trip_points. At one time, this
workaround did seem to work. However, it stopped working when that file was
made read-only. Does anyone know why the trip_points file was made read-only
and why the trip points seem to be reading so ridiculously low?
--
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.
14 years, 11 months
[Bug 199812] ACPI: Unable to turn cooling device [ffff81007ffa6810] 'on' is spewed repeatedly on the console
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=199812
--- Comment #26 from John Guthrie <guthrie(a)counterexample.org> 2009-05-14 04:03:41 EDT ---
(In reply to comment #23)
> boot option "acpi.power_nocheck=1" doesn't work any more?
It doesn't seem to yet:
leibniz_1005% dmesg | tail
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
leibniz_1006% cat /proc/cmdline
ro root=UUID=bd8c223b-daf4-4636-97bf-8a3ea838b87d rhgb acpi.power_nocheck=1
^^^^^^^^^^^^^^^^^^^^
leibniz_1007% uname -a
Linux leibniz 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009
i686 athlon i386 GNU/Linux
Now looking at the URL in comment #19, it would appear that the patch for the
above kernel command line option was committed to kernel 2.6.28-rc1, whereas
the current kernel version is 2.6.27.21. So we might have to wait until we
have a 2.6.28 kernel before we see any relief for this bug.
--
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.
14 years, 11 months