Disabling hald on SLES10 SP3 s390x architecture
This document (7007621) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 10 Service Pack 3
s390x architecture only
Modern mainframe setups often have a huge number of devices attached and active. While hotplugging (done by udev) is quite important on these systems, activation by a desktop user via hal is rarely needed. To avoid quite expensive CPU cycles by monitoring the system for hardware changes and to speed up the boot process, hald can be disabled. This TID explains how.
An updated "sysconfig" rpm package needs to be installed to the system. The rpm is not distributed as a maintenance update. Customers are advised to contact Novell Technical Services to request a Problem Temporary Fix (PTF) package.
Once the sysconfig PTF is installed the file /etc/init.d/network has to be edited. Move the word "haldaemon" from the "Required-Start" line to the "Should-Start" line, like in the following example:
# Required-Start: $local_fs dbus
# Should-Start: isdn haldaemon
Afterwards save the file. To disable hald in the running system, issue the command "rchal stop". In order to prevent the hal daemon from starting at next system startup run the command "insserv -r haldaemon".
Please be aware, that some packages like YaST and NetworkManager depend on hal. If you want to use them, do not disable hal.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7007621
- Creation Date:
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server
< Back to Support Search
For questions or concerns with the SUSE Knowledgebase please contact: firstname.lastname@example.org