Vanilla Netrek Server Development Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[VANILLA-L:1351] INL server installation
While comiling ntserv, just before the link:
ctags cluecheck.c coup.c data.c death.c detonate.c enter.c findslot.c getentry.c getname.c getship.c input.c interface.c main.c orbit.c phaser.c plasma.c redraw.c reserved.c sintab.c socket.c genspkt.c smessage.c startrobot.c timecheck.c torp.c util.c warning.c ping.c getpath.c features.c distress.c transwarp.c gencmds.c ntscmds.c openmem.c feature.c queue.c slotmaint.c wander2.c sysdefaults.c data.h defs.h planets.h struct.h packets.h copyright.h
Duplicate entry in file getentry.c, line 211: if
Second entry ignored
Duplicate entry in file getentry.c, line 239: for
Second entry ignored
Duplicate entry in files interface.c and getentry.c: if (Warning only)
Duplicate entry in file orbit.c, line 41: RETURN_IF_VACANT
Second entry ignored
Duplicate entry in file socket.c, line 1770: handleReserved
Second entry ignored
Duplicate entry in files warning.c and interface.c: new_warning (Warning only)
Duplicate entry in file warning.c, line 178: warning
Second entry ignored
Duplicate entry in files distress.c and warning.c: warning (Warning only)
Duplicate entry in file defs.h, line 66: MATH_ERR_CHECK
Second entry ignored
Duplicate entry in files defs.h and orbit.c: planet_ (Warning only)
Duplicate entry in files defs.h and orbit.c: player_ (Warning only)
Duplicate entry in files defs.h and orbit.c: isAlive (Warning only)
I don't know if that represents a real problem.
install-sh has not solved the install problem; it's still found as
./install-sh -c, and the subdirectories still can't see it.
Once the links are made, the installation actually works, but it takes a
while to do that by hand. On Solaris, at least, those appear to be the only
installation problems.
It would be nice if there were a configure option for --enable-inl which
installed a sysdef with INL=1.
Comments on stats, and game ends in general:
I think at the end of an INL game, the INL robot should call a perl script,
probably called end_tourney.pl, which will then take care of all end-game
related stuff. Except for moving the log files.
Usage: end_tourney.pl [-register] [pid]
So, the server should move INL_log and the others to INL_log.<pid>, and
then run "end_tourney.pl <pid>"; end_tourney.pl will then parse INL_log.<pid>
and mail the PWstats (and the human-readable INL_log, once we have one) to
statboys@csua.berkeley.edu if -register was used.
-Tom
+
++ Vanilla-l Mailing List ++
To unsubscribe: send "unsubscribe vanilla-l" to majordomo@real-time.com
For more information: http://archives.real-time.com