User`s guide

ManualsBrandsRed Hat ManualsConsumer electronicsENTERPRISE 5.4 RELEASE NOTES

??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????+???????????????????????×?????????????????????????????????????????????????−26217

Known Issues

RedHawk Linux Version 5.4 Release Notes 77

9.0. Known Issues

Special consideration should be given to the following areas.

BIOS “Console Redirection”

The “Console Redirection” BIOS feature, when enabled, has been observed to interfere with the

proper operation of the integrated VGA video and the XFree86 X server with some iHawk

platforms, such as the Dell PowerEdge

6650 (iHawk Model HQ665).

NMI Button

Using the NMI button on the processor enters kdb on the console when configured. It cannot

be used, however, to step repeatedly through an error condition.

kdb and USB Keyboards

While kdb does have some support for USB keyboards, it is found not to be reliable and is not

supported in the RedHawk debug kernel. On systems with a USB keyboard, it is recommended

that a serial console be configured and kdb used over the serial port. See Appendix H of the

RedHawk Linux User’s Guide for instructions for setting up the serial console.

PAM Capabilities

• Note that in order to use the pam_capability(8) feature with ssh, the

/etc/ssh/sshd_config file must have the following option set:

UsePrivilegeSeparation no

• Using Kerberos telnet services with PAM is not recommended. If krb5-telnet is on and

Kerberos is not properly configured, the following error will occur upon logging in via

telnet:

while getting initial credentials

The krb5-telnet xinetd service should be disabled:

chkconfig krb5-telnet off

sadc(8) Issue

When a system configuration change is made that affects the number of CPUs (for example

when booting with a uniprocessor kernel or changing hyper-threading configuration), the

sadc(8) (sar data collector) program cannot successfully write data in the daily data file

/var/log/sa/sa?? (?? is the day of the month). This results in crond sending an email

every ten minutes to root@localhost with the following message:

Cannot append data to that file

To eliminate the email, remove or move the /var/log/sa/sa?? file for the current date.