oculus.log purpose needs rethink--see notes here

[GoogleCodeExporter]

not so useful for debug, since not cummulative, not catching all errors
but good to be small so can be viewed at client, see other user activity, etc.
maybe write same info to jvm.stdout, so can be used as complete debug

Original issue reported on code.google.com by skyz...@gmail.com on 28 Apr 2011 at 2:54

[GoogleCodeExporter]

idea: eliminate oculus.log, write all messages to stdout, add "OCULUS:" prefix? 
 (so stdout file can be parsed and only OCULUS messages sent to client when 
clicks 'server log').
This will enable:
-end users only need to send stdout to tech support
-don't have to solve issue of oculus.log being erased/overwritten on server 
restart

Original comment by skyz...@gmail.com on 30 May 2011 at 9:37

[GoogleCodeExporter]

Original comment by skyz...@gmail.com on 30 May 2011 at 9:38

• Changed title: oculus.log purpose needs rethink--see notes here

[GoogleCodeExporter]

Agreed, slowly start removing as we go. I'll get "tail" working on command line 
too. 

Original comment by brad.zdanivsky on 17 Nov 2011 at 1:00

[GoogleCodeExporter]

like?

System.out.println("OCULUS: address [" + clientSocket + "] message [" + str + 
"]");

Original comment by brad.zdanivsky on 17 Nov 2011 at 1:07

[GoogleCodeExporter]

Original comment by skyz...@gmail.com on 31 Jan 2012 at 1:07

• Changed state: Fixed