Red Hat ENTERPRISE LINUX 5.5 - S 2010, Руководство пользователя

Страница: 263 / 470

sysklogd
253
interpreted, and access was not granted to users from non-TTY connections. The sudo utility now
correctly sets the !requiretty option for LDAP users, and they can connect normally. (
BZ#521903
2023
)
* the #includedir directive includes the contents of external directories in the current file. The directive
was not supported in the sudoers file and sudo utility, and as a result external settings files could not
be included. The sudo utility now supports the #includedir directory, and external settings files can be
used in the sudoers file. (
BZ#538700
2024
)
* a bug in the realloc() function caused sudo to crash with a segfault when using a sudoers file with
a deep #include structure. This update corrects this. Note: the hard limit of 128 nested include files
(enforced to prevent #include file loops) remains. (
BZ#561336
2025
)
All users of sudo are advised to upgrade to this updated package, which resolves these issues.
1.196. sysklogd
1.196.1. RHBA-2010:0211: bug fix update
An updated sysklogd package that fixes various bugs is now available.
The sysklogd package contains two system utilities (syslogd and klogd) which provide support
for system logging. Syslogd and klogd run as daemons (background processes) and log system
messages to different places, like sendmail logs, security logs, error logs, etc.
This update addresses the following issues:
* the Red Hat Enterprise Linux syslogd init script creates files which are readable by the root user only
whereas the sysklogd(8) man page indicated that "If a file is created it is world readable". The man
page has been updated with the correct information. (
BZ#460232
2026
)
* the "-S" option was added to sysklogd 1.4.1-40, however, this option is not displayed in the
"SYNOPSIS" section of the sysklogd man page. This has the potential to mislead users who use the
man page for help. The "-S" option has now been added to the "SYNOPSIS" section of the sysklogd
man page. (
BZ#471174
2027
)
* when syslogd was started using the "-m" option with a non-zero argument, the "errno" value of
"select" was checked by the functions that log the "MARK" message after the value had been reset
from "EINTR" to "EINVAL". This resulted in an incorrect message being logged to "/var/log/messages"
of the form; "syslogd: select: Invalid argument". A patch has been applied to store the value of "errno"
in a temporary variable prior to it being reset and testing this stored value against "EINTR" for logging
purposes. The error message no longer appears in "/var/log/messages" when a non-zero argument is
passed to the "-m" option. (
BZ#472875
2028
)
* syslogd.conf would cause a memory leak by forwarding messages to its IP address, for example
"*.*@192.168.122.5". This would result in processes being terminated by the "OOM killer" to free up
memory. A patch has been applied to ensure that messages are not self-forwarded. (
BZ#481600
2029
)
2023
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=521903
2024
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=538700
2025
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=561336
2026
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=460232
2027
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=471174
2028
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=472875
2029
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=481600