Page 1 of 3
Suddenly Segfaulting Client
Posted: Sun Feb 20, 2005 2:45 pm
by Rednaxela
Well... crossfire (gtk client) was working perfectly for me yesterday, then suddenly, when I start it up, it segfaults right after the splash screen
I try everything I can think of and it still segfaults, even when I delete my .crossfire directory with all it's settings to reset it's settings
The client version is "GTK Unix Client 1.7.0"
I think I'm going to try reinstalling from cvs soon, or perhaps live with the horror of cfclient.
Oh wait, cfclient is also segfaulting suddenly too
Posted: Sun Feb 20, 2005 3:08 pm
by Rednaxela
Interesting
... Something must be screwy with the metaserver right now. because I was able bypass the segfault by adding
to the command line...
Could somebody please fix the metaserver
:?::!:
EDIT: I finally got all my settings fixed from the messing with my .crossfire in attempts to fix it. Currently running with the "-server" parameter still.
Posted: Sun Feb 20, 2005 3:16 pm
by Casper
bensnoodle overfilled the number of servers cf client can handle.
Two things need fixing:
1) metaserver should detect that the server is already on the list and merge duplicate entries
2) client should cope with more servers
Posted: Sun Feb 20, 2005 5:52 pm
by cavesomething
addition to list:
3. Servers shouldn't hang around after not being up for several hours.
Posted: Sun Feb 20, 2005 6:04 pm
by Casper
Is it possible to do ICQ-like keep-alive packets? So if servers don't check in every n seconds/minutes we decide they are down? That would require changing the server code too though...
Posted: Sun Feb 20, 2005 6:52 pm
by Rednaxela
Another addition:
4. Get the bensnoodle admin to stop the crashing server
Posted: Sun Feb 20, 2005 7:13 pm
by cavesomething
I did look briefly at the metaserver script, there is a check to blacklist servers calling themselves your.hostname.here
maybe Ben's noodle should be similarly blacklisted?
Posted: Sun Feb 20, 2005 8:29 pm
by Rednaxela
cavesomething wrote:maybe Ben's noodle should be similarly blacklisted?
At least until the admin gets the crashing fixes...
Posted: Mon Feb 21, 2005 5:47 am
by Casper
That is a workaround. What if another server starts crashing? What if a malicious individual fills up the metaserver with rubbish? The metaserver script needs a proper fix, one that will detect downed servers and not include them.
Posted: Mon Feb 21, 2005 6:18 am
by bort
Not to mention running a code checksum that identifies that the server is indeed a CF server, and a checker mechanism that removes entries that are repeated, diff ip address or no diff ip address.