Lon Hohberger wrote:
>>> Well, they people that set that system up are a bit strange.
>>> They have runlevel 5 as initdefault, but the system does not show a
>>> graphical login at boot.
>>> (startx works, though)
>>
>> That's weird, but certainly not the problem. Although, it might be
>> related somehow... clumanager doesn't start, and X doesn't start, but
>> both *should*.
>
>Sounds like inittab weirdness - I saw symptoms like this a few times while
teaching class when students would do stuff like:
>
>id:5:initdefault:
>
># System initialization.
>si::sysinit:/etc/rc.d/rc.sysinit
>
>l0:0:wait:/etc/rc.d/rc 0
>l1:1:wait:/etc/rc.d/rc 1
>l2:2:wait:/etc/rc.d/rc 2
>l3:3:wait:/etc/rc.d/rc 3
>l4:4:wait:/etc/rc.d/rc 4
>l5:5:wait:/etc/rc.d/rc 3 <------
>l6:6:wait:/etc/rc.d/rc 6
>...
>
>When attempting to change their default runlevel.
>
That trick sounds horribly familiar... ( Sorry, NDA ;-) )
Checked, but this is not the case (It's much more fun to redirect runlevels
to 6 or 0 :-D
[root@nzcs1 etc]# grep :5 /etc/inittab
id:5:initdefault:
l5:5:wait:/etc/rc.d/rc 5
x:5:respawn:/etc/X11/prefdm -nodaemon
>It makes life kinda exciting if things are disabled (K links) in rc3.d but
enabled (S links) in rc5.d - runlevel/who -r etc. report
>one thing, but the services started are those belonging to the other
runlevel.
That's cute, checked and passed:
[root@nzcs1 etc]# find . -type l -ls |grep cluster
2796355 0 lrwxrwxrwx 1 root root 17 Jun 3 2004
./rc.d/rc0.d/K01cluster -> ../init.d/cluster
2976480 0 lrwxrwxrwx 1 root root 17 Jun 3 2004
./rc.d/rc1.d/K01cluster -> ../init.d/cluster
3009017 0 lrwxrwxrwx 1 root root 17 Jun 3 2004
./rc.d/rc2.d/S99cluster -> ../init.d/cluster
3026727 0 lrwxrwxrwx 1 root root 17 Jun 3 2004
./rc.d/rc3.d/S99cluster -> ../init.d/cluster
3042076 0 lrwxrwxrwx 1 root root 17 Jun 3 2004
./rc.d/rc4.d/S99cluster -> ../init.d/cluster
3058185 0 lrwxrwxrwx 1 root root 17 Jun 16 2005
./rc.d/rc5.d/S99cluster -> ../init.d/cluster
3090980 0 lrwxrwxrwx 1 root root 17 Jun 3 2004
./rc.d/rc6.d/K01cluster -> ../init.d/cluster
>It's also worth checking grub.conf incase they've overridden initdefault
from the kernel command line.
Foiled again!
>From /boot/grub/grub.conf:
default=13
fallback=10
# This entry (no. 10) added by Proliant HBA install script
title HP-2.4.9-e.24enterprise-1
root (hd0,0)
kernel /vmlinuz-2.4.9-e.24enterprise ro root=/dev/cciss/c0d0p5
hda=ide-scsi
initrd /HP-initrd-2.4.9-e.24enterprise.img
# This entry (no. 13) added by Proliant HBA install script
title HP-2.4.9-e.24enterprise-2
root (hd0,0)
kernel /vmlinuz-2.4.9-e.24enterprise ro root=/dev/cciss/c0d0p5
hda=ide-scsi
initrd /HP-initrd-2.4.9-e.24enterprise.img-0
(I'm still trying to figure out WTF HP did with my grub.conf)
I -DO- appreciate all the help I have received so far.
This is an interesting little trick they must have pulled...
Regards,
Kit
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
