Can anyone forsee possible problems with moving hotboot recover into the database loading, and putting it before load_world? Like such:

      if( fCopyOver )
	{
       boot_log( "Initiating hotboot recovery." );
       hotboot_recover();
    boot_log( "Loading world state..." );
    load_world( supermob );
	}

I can't think of any problems, and besides some log spam, there doesn't seem to be a problem with it so far. Anyone know anything?

Log spam is usually an inditaction of something not right, and therefore I would consider it a problem

But, yes. There is one legitimate concern to watch for. Muds with I3 installed will crash if you don't also move the I3_main call. That call *MUST* be before you initiate the hotboot_recover. If it's not, the game will crash at bootup. This is why hotboot_recover is the last thing called in init_mud in AFKMud.

As a side note - I3 or IMC2 really should be positioned to start sometime AFTER you do the boot_db. If something should go wrong in your boot sequence, at least then it doesn't spam the routers while you figure out the problem with your areas or something.

Thanks for the info, but I'm not using I3 or IMC2, but if I do install it, I'll keep that in mind, thanks. The spam that I see inside my client is just the log messages associated with the rest of the boot process, mostly in load_world and such. I've modified my boot sequence to log into the boot file for dmesg, and thats the spam.

So far, I can't see any problems with it. The main reason for this is to preserve ch->master of mobs.

Thanks muchly for all the help, though.