[gentoo-catalyst] gconfd-2 strikes again

[Robert Paskowitz]

Going for another CD build with a newer snapshot, and catalyst 1.1.7, 
I've hit the gconfd-2 wall again.

Initial problem:

The check to see if gconfd-2 is running occurs outside the chroot, 
which, on it's own is fine. The problem is that gconftool-2 is run from 
outside the chroot, which is not necesarilly installed on the host 
system. Even providing a full path is not sufficient, since the linked 
libraries can be in the wrong place. This is an easy fix, the code 
segment can be moved to the end of 
/usr/lib/catalyst/targets/livecd-stage1/livecd-stage1-chroot.sh to have 
it run within the chroot.

Subsequent problem:

gconftool-2 does not actually shutdown gconfd-2. As shown by 
`gconftool-2 -p; echo $?` (ping), to see if gconfd-2 is running, 
gconftool-2 return '2' which following the help means it does not 
believe gconfd-2 is running. This would explain why my attempts with 
'gconftool-2 --shutdown' failed. From the help, it says that 
'gconftool-2 --shutdown' should only be used with good reason, which 
makes me believe it does not perform a very clean shutdown. For that 
reason, I am personally going back to something along the lines of 
killall -9 gconfd-2.

At a minimum, the code segment in 
/usr/lib/catalyst/targets/livecd-stage1/livecd-stage1.sh should be 
moved, and I can provide a patch if necessary, but since gconftool-2 
--shutdown does not appear to work, I think one of the older methods 
should be reverted to.


Robert


P.S. -- I've only tried the gconftool-2 --shutdown manually chrooting 
in, after livecd-stage1 failed. I am having a go with the code in 
/usr/lib/catalyst/targets/livecd-stage1/livecd-stage1-chroot.sh to see 
if maybe it will work then.
--
gentoo-catalyst@g.o mailing list