I have seen this hang few times after activating 10-15 modules. A question - is a sleep 5 necessary in all cases? it will slow down the shutdown procedure a bit.
It is average time - not solution for all possible big numbers modules in memory
May be sync && sync ; sleep 1 ; sync && sync will be also ok for most situation
But need to test
Also, when you activate 006-devel package then you wont be able to deactivate it (old bug present also in slax-6.1.2 ). I think it's about /etc/ld.so.conf or /etc/ld.so.cache which are present in devel module, so when you insert it - /sbin/ldconfig is run (have a look at very few last lines of /usr/bin/activate script)
Did you find a solution to this?
you are absolutely right it is of /etc/ld.so.conf
The solution have to be opposite activation code
in deactivate script something like this
Code: Select all
if [ -e "$MOD/etc/ld.so.conf" -o -e "$MOD/etc/ld.so.cache" ]; then
echo "Module contains ld.so.conf or ld.so.cache, updating libs cache..."
diff ld.so.conf /etc/ld.so.conf | grep ">" | sed "s|> ||g" > /etc/ld.so.conf.new
rm -f /etc/ld.so.conf
mv /etc/ld.so.conf.new /etc/ld.so.conf
But not sure - neet to check
Last question - i can remember when on slax forum you had some troubles with conky and Imlib and you were proposing of forcing updates of shared library links after each module insertion. I have added 'ldconfig' to rc.S and was not able to reproduce this error on my PC. Do you know if conky/Imlib bug is still present on your machines?
It was in 64-bit
Now I use 32
When I have test 64 bit I will check