As far as the boot.log goes–If you do not have a log viewer, you can issue the following:
tail -n 500 boot.log > myTempLog
to save the last 500 lines to myTempLog
You will have to adjust the -n flag to catpure the correct start point for the last boot.
I get the feeling that we are dealing with a dependency issue here. I suspect that the messenger script is being called before all env vars are set or something. Make sure that JAVA_HOME and all env vars are set before the messenger script is called. The init process will run before your login shell, so if you set your JAVA_HOME in ~/.profile or ~/.bashrc or such, init will not see it. Not sure if /etc/profile is sourced before or after init. It wouldn’'t hurt to put the env vars in the actual startup script itself–or at least source them from their current location.
As for the SNN/KNN I was referring to–
The “S” refers to start, “K” to kill. The “NN” refers to a numeric order in which to call the (symlinked) scripts. For example, the symlinks:
would start seviceA, serviceB, serviceC in that order based on the order of the “NN” portion of the symlink name. If serviceA should happen to depend on serviceB, then serviceA will fail because serviceB does not get called until after serviceA. You should see this convention used in your rc subdirectories (where the symlinks live.) If not, then mandrake does not support this (LSB) standard.
Try “locate S01” to see if any such exist on your machine.
I might also suggest adding some debug stuff to the jive messenger script itself to make sure that it can see all required vars when it is called.
echo $(date “+%F %H:%M:%S”) > /some/writable/location/myStartLog
echo $JAVA_HOME >> /some/writable/location/myStartLog
echo $CLASSPATH >> /some/writable/location/myStartLog
This will varify the proper env vars are being seen and whether or not the messenger script is actually being called.
Sorry, I can’‘t be of more help, but I am not familiar with Mandrake’‘s boot process. I would definitley look into Mandrake’'s documentation on init scripts and compare that with the script you obtained from jive. It may be the obtained script is not appropraite for your version of Mandrake.