Test Page - Revision history

BlueWall: /* JSON User SimStats */

2015-01-02T01:17:24Z

‎JSON User SimStats

BlueWall: /* JSON User SimStats */

2014-12-30T21:27:54Z

‎JSON User SimStats

Show changes

BlueWall: moved User talk:BlueWall to Test Page: See if this creates a page

2012-07-10T16:59:22Z

moved User talk:BlueWall to Test Page: See if this creates a page

BlueWall: /* TESTING */ new section

2012-07-10T16:58:44Z

‎TESTING: new section

BlueWall: /* Using shell environment variables in OpenSim configuration */

2011-11-23T18:13:07Z

‎Using shell environment variables in OpenSim configuration

BlueWall: /* Using shell environment variables in OpenSim configuration */

2011-11-23T18:11:57Z

‎Using shell environment variables in OpenSim configuration

BlueWall: /* Using shell environment variables in OpenSim configuration */ new section

2011-11-23T18:11:03Z

‎Using shell environment variables in OpenSim configuration: new section

Justincc at 20:22, 10 October 2011

2011-10-10T20:22:39Z

BlueWall: /* JSON User SimStats */

2011-05-06T11:01:14Z

‎JSON User SimStats

BlueWall: /* Starting and stopping the grid server via script */

2011-02-13T17:37:41Z

‎Starting and stopping the grid server via script

@@ Line 35: / Line 35: @@
   <source lang="html4strict">
 <!DOCTYPE HTML>
 <html>
@@ Line 40: / Line 41: @@
 <title>JSON Test</title>
 <script src="https://code.jquery.com/jquery-2.1.3.min.js"></script>
 <script type="text/javascript" src="http://www.google.com/jsapi"></script>
 <script type="text/javascript" language="JavaScript">
 SimFPS = 0;
 PhyFPS = 0;
@@ Line 51: / Line 52: @@
 Version = "";
-var timer = new Timer({
+setInterval(function(){
-tick : 1,
-ontick : function (sec) {
 $.getJSON(
    "http://ascent.bluewallgroup.com:9100/jsonSimStats/?callback=?",
@@ Line 66: / Line 65: @@
    drawChart();
    setTags();
-   });
+   })}, 3000
-},
+);
-onstart : function() {
-console.log('timer started');
-},
-onend : function() {
-          console.log("Timer stopped");
-          this.start(100);
-−
-});
 google.load("visualization", "1", {packages:["gauge"]});

← Older revision		Revision as of 16:58, 10 July 2012
Line 214:		Line 214:

	Have Fun!		Have Fun!
		+
		+	== TESTING ==
		+
		+	This is a test

@@ Line 173: / Line 173: @@
 </source>
+<source lang="bash">
 # You can see your HOSTNAME (It will be set by the system)...
 echo $HOSTNAME
 OSERV_00
+</source>
 In the ini you will include an [Environment] section...
+<source lang="ini">
 [Environment]  ; Our Environment section that defines the shell variables we are interested in
 RT_ZONE=""     ; We might use a zone to setup an instance of OpenSim on a server
@@ Line 191: / Line 191: @@
 [DatabaseService]
 ConnectionString = "Data Source=localhost;Database=${Environment|RT_ZONE};User ID=username;Password=userpass;" ; Here too
+</source>
 When OpenSim picks up the variables in your shell and processes all the configurations, the variable keys will be filled in with the variables picked up from the shell ...
+<source lang="ini">
 [Environment]  ; Our Environment section that defines the shell variables we are interested in
 RT_ZONE=""     ; We might use a zone to setup an instance of OpenSim on a server
@@ Line 207: / Line 207: @@
 [DatabaseService]
 ConnectionString = "Data Source=localhost;Database=Zone_00;User ID=username;Password=userpass;" ; Here too
+</source>

@@ Line 169: / Line 169: @@
 In your shell you will export your values and check the ones you want to use that are predefined by your system ...
+<source lang="bash">
 export RT_ZONE=Zone_00
+</source>

← Older revision		Revision as of 18:11, 23 November 2011
Line 162:		Line 162:

	</source>		</source>
		+
		+	== Using shell environment variables in OpenSim configuration ==
		+
		+	We will need to use two new things in our configurations: a section [Environment] to tell us what variables we need to look at in the shell and we will need to use the Nini key expansion. Nini, can have keys that look like ${SECTION\|VARIABLE} and can expand those to the variables we assign.
		+
		+	In your shell you will export your values and check the ones you want to use that are predefined by your system ...
		+
		+
		+	export RT_ZONE=Zone_00
		+
		+
		+
		+	# You can see your HOSTNAME (It will be set by the system)...
		+	echo $HOSTNAME
		+	OSERV_00
		+
		+
		+	In the ini you will include an [Environment] section...
		+
		+	[Environment] ; Our Environment section that defines the shell variables we are interested in
		+	RT_ZONE="" ; We might use a zone to setup an instance of OpenSim on a server
		+	HOSTNAME="" ; We might be interested in obtaining the host's name
		+
		+	[Startup]
		+	regionload_regionsdir=/home/opensim/etc/Regions/${Environment\|RT_ZONE}/ ; We set our regionload_regionsdir using the variables
		+	ConsolePrompt = "${Environment\|HOSTNAME}:${Environment\|RT_ZONE} "
		+
		+	[DatabaseService]
		+	ConnectionString = "Data Source=localhost;Database=${Environment\|RT_ZONE};User ID=username;Password=userpass;" ; Here too
		+
		+
		+
		+
		+	When OpenSim picks up the variables in your shell and processes all the configurations, the variable keys will be filled in with the variables picked up from the shell ...
		+
		+	[Environment] ; Our Environment section that defines the shell variables we are interested in
		+	RT_ZONE="" ; We might use a zone to setup an instance of OpenSim on a server
		+	HOSTNAME="" ; We might be interested in obtaining the host's name
		+
		+	[Startup]
		+	regionload_regionsdir=/home/opensim/etc/Regions/Zone_00/ ; We set our regionload_regionsdir using the variables
		+	ConsolePrompt = "OSERV_00:Zone_09 "
		+
		+	[DatabaseService]
		+	ConnectionString = "Data Source=localhost;Database=Zone_00;User ID=username;Password=userpass;" ; Here too
		+
		+
		+
		+
		+	This is a pretty good start. I think there will be a couple of places we might be able to use this to help us setup really flexible configuration systems for OpenSim.
		+
		+	Have Fun!

@@ Line 1: / Line 1: @@
+'''As of 2011-10-10 I copy/pasted this over to the linked [[UXSimStatus]] for further change/editing -- [[User:Justincc|Justincc]] 20:22, 10 October 2011 (UTC)'''
-−
-−

← Older revision		Revision as of 17:37, 13 February 2011
Line 3:		Line 3:


−	~~== Starting and stopping the grid server via script ==~~
−	~~<source lang="bash">~~
−	~~#!/bin/bash~~
−	#
−	#
−	~~OSDIR=/opt/OpenSim~~
−	~~OSRUNDIR=lib/opensim/trunk/bin~~
−	~~export SCREENDIR=$OSDIR/var/run/screen~~

−	~~case "$1" in~~
−
−	~~'start')~~
−	~~echo "Starting Grid Services"~~
−
−	~~for i in BWG~~
−	do
−	~~kill `ls $SCREENDIR/*.$i \|~~
−	~~cut -d'/' -f7 \|~~
−	~~sed s/[^0-9]//g`~~
−	~~done~~
−	~~screen -wipe~~
−	~~sleep 3~~
−
−	~~cd $OSDIR/$OSRUNDIR~~
−
−	~~echo "User Server..."~~
−	~~screen -dmS BWG -t US mono OpenSim.Grid.UserServer.exe &~~
−	~~screen -S BWG -X hardstatus alwayslastline "%{=b}%{G} %H Screen(s): %{b}%w %=%{kG}%C%A %D, %M/%d/%Y "~~
−	~~sleep 5~~
−	~~echo "Grid Server..."~~
−	~~screen -S BWG -X screen -t GS mono OpenSim.Grid.GridServer.exe &~~
−	~~sleep 5~~
−	~~echo "Asset Server..."~~
−	~~screen -S BWG -X screen -t AS mono OpenSim.Grid.AssetServer.exe &~~
−	~~sleep 5~~
−	~~echo "Inventory Server..."~~
−	~~screen -S BWG -X screen -t IS mono OpenSim.Grid.InventoryServer.exe &~~
−	~~echo "Messaging Server..."~~
−	~~screen -S BWG -X screen -t MS mono OpenSim.Grid.MessagingServer.exe &~~
−	;;
−
−	~~'stop')~~
−	~~for i in BWG~~
−	do
−	~~kill `ls $SCREENDIR/*.$i \|~~
−	~~cut -d'/' -f7 \|~~
−	~~sed s/[^0-9]//g`~~
−	~~done~~
−	~~screen -wipe~~
−	;;
−
−	~~'screen')~~
−	~~screen -r BWG~~
−	;;
−
−	~~esac~~
−	~~</source>~~

	== JSON User SimStats ==		== JSON User SimStats ==