IMC2 - Potential Bug?
< Newer Topic
:: Older Topic >
Pages:<< prev 1 next >>
#1 Feb 15, 2006 4:43 am
Last edited Feb 15, 2006 4:43 am by enderandrew
GroupMembers
Posts8
JoinedFeb 8, 2006
I'm manually adding IMC2 support, and while I'm at it, I'm comparing my changes to SWFoTEFUSS to make sure I've got it right.
The instructions in the snippet say:
Yet, in comm.c, you have the addition below, not above the boot_db call.
The instructions in the snippet say:
This next part is somewhat tricky. If copyover_recover is called in db.c as is the usual case in
most default installs, you need to place the following BEFORE the boot_db call. If it is listed
somewhere here in comm.c, the following needs to be placed ABOVE it. Either way, imc_startup needs
to be called BEFORE copyover_recover or your mud WILL crash every time you do a copyover.
Yet, in comm.c, you have the addition below, not above the boot_db call.
boot_db( fCopyOver ); log_string( "Initializing socket" ); if( !fCopyOver ) /* We have already the port if copyover'ed */ { control = init_socket( port ); } #ifdef IMC /* * Initialize and connect to IMC2 */ imc_startup( FALSE, imcsocket, fCopyOver ); #endif
#2 Feb 15, 2006 8:21 pm
Black Hand
GroupAdministrators
Posts3,685
JoinedJan 1, 2002
Take a look again.
The call to imc_startup is in the proper place.
/* * Run the game. */ log_string( "Booting Database" ); boot_db( fCopyOver ); log_string( "Initializing socket" ); if( !fCopyOver ) /* We have already the port if copyover'ed */ { control = init_socket( port ); } #ifdef IMC /* * Initialize and connect to IMC2 */ imc_startup( FALSE, imcsocket, fCopyOver ); #endif if( fCopyOver ) { log_string( "Initiating hotboot recovery." ); hotboot_recover( ); }
Either way, imc_startup needs
to be called BEFORE copyover_recover or your mud WILL crash every time you do a copyover.
The call to imc_startup is in the proper place.
#3 Feb 16, 2006 1:43 am
GroupMembers
Posts8
JoinedFeb 8, 2006
It says in one sentence it needs to be before boot_db, and in the next sentence it says it needs to be before the copyover/hotboot_recover.
You have it before the recover call, but not before the boot_db call.
You have it before the recover call, but not before the boot_db call.
#4 Feb 16, 2006 6:18 am
Black Hand
GroupAdministrators
Posts3,685
JoinedJan 1, 2002
No.
It says if copyover_recover is called from db.c that you need to put it above the call to boot_db.
If copyover_recover is called from comm.c, as it is with FUSS, you need to put the call above that.
So there is no bug.
It says if copyover_recover is called from db.c that you need to put it above the call to boot_db.
If copyover_recover is called from comm.c, as it is with FUSS, you need to put the call above that.
So there is no bug.
Pages:<< prev 1 next >>