[bf1942] Peter: What about GLIBC <= 2.2?

Peter Chang peter.chang at dicecanada.com
Fri Mar 12 08:51:43 EST 2004


From: Kingsley Foreman [mailto:kingsley at internode.com.au]
Subject: Re: [bf1942] Peter: What about GLIBC <= 2.2?

it might be drunk but that made no sense to me :)

i was sort of thinking out loud (and smacking my forehead)
 
 ----- Original Message ----- 

From: Peter Chang <mailto:peter.chang at dicecanada.com>  
To: 'bf1942 at icculus.org' <mailto:'bf1942 at icculus.org'>  
Sent: Friday, March 12, 2004 11:04 PM
Subject: RE: [bf1942] Peter: What about GLIBC <= 2.2?


From: Kingsley Foreman [mailto:kingsley at internode.com.au]
Sent: Thursday, March 11, 2004 10:55 PM
To: bf1942 at icculus.org <mailto:bf1942 at icculus.org> 
Subject: Re: [bf1942] Peter: What about GLIBC <= 2.2?



 - server may have a default (system dependent ip), but if the user 
      wants to bind to a specific one, please do it. 
      (thanks to kingsley foreman) 
 
still not working
still isn't binding ASE or gamespy to the ip address (ase not responding and
gamespy still not showing up when ip is assigned)
 

hmmm... that works for me right now. wait.... hmm.... it seems that the
gameserver and setup have different ideas about the ip address.  

 internally the gameserver returns its address as an ip/port pair while
setup keeps these two distinct. when moving some code around for the
dedicated server i used one value because it was handy (and why would you
pass an ip/port pair and a port at the same time?

remote console is working now, but as you said serverstatus stops when
connected

actually it was only when i went home last night that the actual message
handling logic for the remote console is nightmare so something is looping
when it shouldn't.  
 

 
there's some other bug that i still have to track down. i only tested
enabling when checking in (naively thinking that, that was the end of my
problems)
 
\p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/bf1942/attachments/20040312/2b347269/attachment.htm>


More information about the Bf1942 mailing list