Log interesting system information on server startup; logging at start of

init() also provides immediate feedback re: the server starting up and a
timestamp in the log against which subsequent action timeliness may be
weighed.  I suspect mdb will decide this is better off residing in the
Yohoho-specific server and outputting to something like the server state
audit log, but I like it here and so I've forged ahead.  If this does get
the axe, I still claim that logging "Server starting up..."  as the first
business in init() is useful and desirable.


git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2143 542714f4-19e9-0310-aa3c-eee0fc999fb1

src/java/com/threerings/presents/server/PresentsServer.java

@@ -1,5 +1,5 @@
 //
-// $Id: PresentsServer.java,v 1.29 2002/12/22 07:27:20 mdb Exp $
+// $Id: PresentsServer.java,v 1.30 2003/01/14 22:36:58 shaper Exp $
 
 package com.threerings.presents.server;
 
@@ -7,6 +7,7 @@ import java.util.ArrayList;
 
 import com.samskivert.util.IntervalManager;
 import com.samskivert.util.StringUtil;
+import com.samskivert.util.SystemInfo;
 
 import com.threerings.presents.Log;
 import com.threerings.presents.client.Client;
@@ -69,6 +70,12 @@ public class PresentsServer
     public void init ()
         throws Exception
     {
+        // output general system information
+        SystemInfo si = new SystemInfo();
+        Log.info("Starting up server [os=" + si.osToString() +
+                 ", jvm=" + si.jvmToString() +
+                 ", mem=" + si.memoryToString() + "].");
+
         // create our distributed object manager
         omgr = new PresentsDObjectMgr();