Login
User Name:

Password:



Register

Forgot your password?
void nanny_get_new_race -- comm.c
Mar 13, 2025 7:08 am
By Elwood
IPv6
Jan 25, 2025 10:45 pm
By Samson
mudstrlcpy and mudstrlcat
Jan 18, 2025 5:23 pm
By Samson
I3 and IMC
Jan 17, 2025 9:35 pm
By Samson
AFKMud 2.5.1
Jan 17, 2025 2:22 pm
By Samson
SWFotEFUSS 1.5.3
Author: Various
Submitted by: Samson
SWRFUSS 1.4.3
Author: Various
Submitted by: Samson
SmaugFUSS 1.9.8
Author: Various
Submitted by: Samson
AFKMud 2.5.2
Author: AFKMud Team
Submitted by: Samson
SmaugFUSS 1.9.7
Author: Various
Submitted by: Samson
Users Online
Anthropic, AhrefsBot, Yandex, Bytespider

Members: 0
Guests: 6
Stats
Files
Topics
Posts
Members
Newest Member
507
3,812
19,722
591
TracySpencer

» SmaugMuds » Codebases » SWFOTE FUSS » IMC2 - Potential Bug?
Forum Rules | Mark all | Recent Posts

IMC2 - Potential Bug?
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Feb 15, 2006 4:43 am   Last edited Feb 15, 2006 4:43 am by enderandrew
Go to the top of the page
Go to the bottom of the page

enderandrew
Fledgling
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:
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

Post is unread #2 Feb 15, 2006 8:21 pm   
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,707
JoinedJan 1, 2002

 
Take a look again.

   /*
    * 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.

Post is unread #3 Feb 16, 2006 1:43 am   
Go to the top of the page
Go to the bottom of the page

enderandrew
Fledgling
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.

Post is unread #4 Feb 16, 2006 6:18 am   
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,707
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.

Pages:<< prev 1 next >>