Description of problem:
The /etc/rc.sysinit script sets RHGB_STARTED=0 but /etc/init.d/functions checks
if it's null (""). It caused a problem with headless nodes imaged with
SystemImager software to hang on boot trying to open
/etc/rhgb/temp/rhgb-console. Removing /etc/rhgb/temp/rhgb-console from the
image solved the problem, but the RHGB_STARTED usage should be fixed to be
Steps to Reproduce:
1. When RHGB is enabled, and it has started, reboot the system. (in the middle
2. Remove the "rhgb" parameter in the boot loader entry (in grub or lilo), so
that the system will not start RHGB.
3. Boot the system. You should see it hang when the first initscript is executed.
Reassigning to initscripts
This problem is fixed in the development tree, and will be resolved in the next
major release of Red Hat Enterprise Linux. Red Hat does not currently plan to
provide a resolution for this in a Red Hat Enterprise Linux update for currently
deployed systems. To get into this situation, you would have to somehow create
an image of a system *while RHGB is running* - the pipe in question is only ever
created on a temporary ramfs filesystem. This is highly unlikely to happen.
With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects.
As a workaround seems to exist for RHEL 5, moving this to RHEL6 and approving.