Vanilla Development Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS update: Vanilla
Date: Thursday February 24, 19100 @ 21:11
Author: cameron
Update of /home/netrek/cvsroot/Vanilla
In directory swashbuckler.fortress.real-time.com:/var/tmp/cvs-serv638
Modified Files:
ChangeLog INSTALL INSTALL.INL
Log Message:
Changes to get 2.9pl5 compiled as an INL server for inl.real-time.com
****************************************
Index: Vanilla/ChangeLog
diff -u Vanilla/ChangeLog:1.62 Vanilla/ChangeLog:1.63
--- Vanilla/ChangeLog:1.62 Tue Jan 11 20:29:50 2000
+++ Vanilla/ChangeLog Thu Feb 24 21:11:43 2000
@@ -1,3 +1,13 @@
+Fri Feb 25 14:03:43 2000 James Cameron <quozl@us.netrek.org>
+
+ * tools/ltd_dump.c: initializer element is not constant.
+
+ * INSTALL: change references to newstartd into netrekd.
+
+ * INSTALL.INL: validate instructions for 2.9pl5 on
+ inl.real-time.com, change references to newstartd into netrekd,
+ add revision header, include LTD_STATS and LTD_PER_RACE
+
Wed Jan 12 11:37:00 2000 James Cameron <quozl@us.netrek.org>
* tools/update.c (makemotd):
@@ -796,4 +806,4 @@
update_sys_defaults in updateMessages to a more appropriate
location - updateClient in socket.c.
- $Id: ChangeLog,v 1.62 2000/01/12 02:29:50 cameron Exp $
+ $Id: ChangeLog,v 1.63 2000/02/25 03:11:43 cameron Exp $
Index: Vanilla/INSTALL
diff -u Vanilla/INSTALL:1.6 Vanilla/INSTALL:1.7
--- Vanilla/INSTALL:1.6 Sat Mar 6 00:51:59 1999
+++ Vanilla/INSTALL Thu Feb 24 21:11:43 2000
@@ -1,6 +1,5 @@
-# $Id: INSTALL,v 1.6 1999/03/06 06:51:59 tanner Exp $
+# $Id: INSTALL,v 1.7 2000/02/25 03:11:43 cameron Exp $
Instructions for installing the Vanilla Netrek Server
-14-Feb-1999
Summary
-------
@@ -10,7 +9,7 @@
(default path is /usr/local/games/netrek)
2) type "make install",
3) "cd" to the path you gave, or /usr/local/games/netrek,
- 4) "./newstartd&" to start the server,
+ 4) "./netrekd" to start the server,
5) use a client to connect to the server.
Details
@@ -60,7 +59,7 @@
If the install worked then go to the installation directory. There are two
programs that should be running all the time. They are:
- 1. newstartd - waits around for a connection from a client. It then forks
+ 1. netrekd - waits around for a connection from a client. It then forks
and execs an ntserv. This also accepts connections from the metaserver
and via telnet for the current player list.
@@ -77,6 +76,7 @@
For assistance, write to vanilla-list@us.netrek.org.
-Developers may wish to subscribe to vanilla-list by sending an empty email
-message to vanilla-list-subscribe@us.netrek.org. No subject or body required.
-See the README for more details and other mailing lists the Vanilla Team offers.
+Developers may wish to subscribe to vanilla-list by sending an empty
+email message to vanilla-list-subscribe@us.netrek.org. No subject or
+body required. See the README for more details and other mailing
+lists the Vanilla Team offers.
Index: Vanilla/INSTALL.INL
diff -u Vanilla/INSTALL.INL:1.2 Vanilla/INSTALL.INL:1.3
--- Vanilla/INSTALL.INL:1.2 Sat Mar 6 00:51:59 1999
+++ Vanilla/INSTALL.INL Thu Feb 24 21:11:43 2000
@@ -1,18 +1,19 @@
+# $Id: INSTALL.INL,v 1.3 2000/02/25 03:11:43 cameron Exp $
Instructions for installing the Vanilla Netrek Server as an INL Server
-15-Feb-1999 cameron@stl.dec.com
Summary
-------
0) choose a place to put the server (e.g. /usr/local/games/netrek)
1) change PKEY in ntserv/defs.h if you have a pickup server too
- 2) type "./configure --prefix=dir" where dir is from step 0
- 3) type "make install"
- 4) "cd /usr/local/games/netrek" (or whatever dir was)
- 5) "vi .sysdef" and set INL=1
- 6) ensure no conflict in .ports with your pickup server if any
- 7) "./newstartd&"
- 8) use a client to connect to the server on port 4566/4577
+ 2) enable LTD_STATS and LTD_PER_RACE in config.h.in
+ 3) type "./configure --prefix=dir" where dir is from step 0
+ 4) type "make install"
+ 5) "cd /usr/local/games/netrek" (or whatever dir was)
+ 6) "vi .sysdef" and set INL=1
+ 7) ensure no conflict in .ports with your pickup server if any
+ 8) "./netrekd" to start the server
+ 9) use a client to connect to the server on port 4566/4577
Details
-------
@@ -22,34 +23,40 @@
0) Don't use the same directory as an existing pickup server.
-1) Changing PKEY in ntserv/defs.h is mandatory if you have a pickup server,
-otherwise the two servers will occupy the same universe, with unexpected
-results. The default is 128. Typically incrementing it will work fine.
+1) Changing PKEY in ntserv/defs.h is mandatory if you have a pickup
+server, otherwise the two servers will occupy the same universe, with
+unexpected results. The default is 128. Typically incrementing it
+will work fine.
-2) No comment.
+2) Enabling LTD_STATS and LTD_PER_RACE in config.h.in before doing the
+configure script ensures that the end of game statistics report works.
3) No comment.
4) No comment.
-5) Setting INL=1 in .sysdef enables the INL robot mode of the server, starting
-the INL robot as soon as the first player joins. Without it, the 4566/4577
-ports will not be opened.
-
-6) If you have a pickup server, you must be sure to remove all the INL ports
-from the .ports file in the pickup server's directory, and restart newstartd
-if you made a material change. You must also remove the pickup and player
-list ports from the .ports file of the INL server. If you don't do this, the
-symptom is a failure of the newstartd process to get going.
-
-7) Yes, you end up with two newstartd processes on your system if you have a
-pickup server. As of 2.9pl0, newstartd writes its process id into the server
-directory as .newstartd.pid, so determining which is which should not be a
-problem.
-
-8) On slow systems, a second client connection may be required. This may be
-a race condition between the startup of the client and the server startup and
-subsequent opening of the queues by the INL robot. The symptom is a "Sorry,
-but you cannot play Xtrek right now" or similar.
+5) No comment.
+
+6) Setting INL=1 in .sysdef enables the INL robot mode of the server,
+starting the INL robot as soon as the first player joins. Without it,
+the 4566/4577 ports will not be opened.
+
+7) If you have a pickup server, you must be sure to remove all the INL
+ports from the .ports file in the pickup server's directory, and
+restart newstartd if you made a material change. You must also remove
+the pickup and player list ports from the .ports file of the INL
+server. If you don't do this, the symptom is a failure of the netrekd
+process to get going.
+
+8) Yes, you end up with two netrekd processes on your system if you
+have a pickup server. As of 2.9pl0, netrekd wrote its process id into
+the server directory as .netrekd.pid, so determining which is which
+should not be a problem.
+
+9) On slow systems, a second client connection may be required. This
+may be a race condition between the startup of the client and the
+server startup and subsequent opening of the queues by the INL robot.
+The symptom is a "Sorry, but you cannot play Xtrek right now" or
+similar.
For assistance, write to vanilla-list@us.netrek.org