More info...
- The temp directory in the admin console *does *dictate where the
rtelogs go.
- As long as
- I set it
to C:\openbd\tomcat\webapps\ROOT\WEB-INF\bluedragon\work\temp
- The work directory ghas a folder called rteLogs in it
then the console can see the log files as this is where it expects them to
be.
- Any change to the setting only seems to take effect after a Tomcat
restart and this confused me for a while.
The same setting does not tell it where to put the other log files. They are
still going where they always did.
If anyone else has this problem I schedule the following bat file to run
every 10 minutes:
Rem This is used because the bd admin console does not point to the same
place as the log files are created.
Rem Issue raised on the following forum
https://groups.google.com/d/topic/openbd/0kvcVV36nd8/discussion
Rem No fix as yet (1st feb 2011) so this workaround put in
Rem The rteLogs can be put where they should by updating the temp directory
in the admin console to this value:
Rem C:\openbd\tomcat\webapps\ROOT\WEB-INF\bluedragon\work
Rem It expects a directory calle rtelogs to be in the work directory
Rem The clutch of remaining log files can be made accessible by the
following RoboCopy command that I schedule to run every 10 minutes
robocopy C:\openbd\logs
C:\openbd\tomcat\webapps\ROOT\WEB-INF\bluedragon\work /e
--
tag/function ref: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
