RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #594034 +++

--- Additional comment from atodorov on 2010-05-31 15:11:16 EEST ---

With anaconda-13.21.48 there's no error message about the missing shared library. However the system will not shutdown:

In the rescue shell type: shutdown -h now  - nothing happens.

The shutdown binary is not part of the install/rescue environment, but it was found on the rescued system (/mnt/sysimage/sbin/shutdown). It can't work since you are not running regular init, but only stripped rescue one.

Use poweroff, reboot or halt to stop the rescue system.

Martin,
poweroff and halt will not work as well if executed while inside the chroot.

No they won't. And never will. At least until we change the init system.

Again.. we do not have any runlevels in rescue, no init socket and we do not accept commands from telinit, so you have to use rescue tools which use proper signaling for rescue mode.

Use poweroff or halt from the rescue environment. It has preference in PATH so you are using rescue stuff over the installed stuff (which is not guaranteed to work at all. And broken system is the reason to run rescue, isn't it).