[Glass] "Transcript enableLoggingToGemLogFileForSession" not working anymore?
Dale Henrichs via Glass
glass at lists.gemtalksystems.com
Thu Feb 2 08:31:10 PST 2017
...oh and logging to the gem log file is enabled by default ...
also, if you use `startTopaz xxx -r` (remote login) the transcript
output shows up in the gem log file ... be aware that gem log files are
automatically deleted upon successful logout (log file is not deleted if
there is an error exit) ... there are ways to arrange to keep all gem
log files if needed ...
Dale
On 2/2/17 5:49 AM, Mariano Martinez Peck via Glass wrote:
> Hi Dale,
>
> Remember some time ago we added #enableLoggingToGemLogFileForSession
> and related methods?
>
> I am trying this simple script on a 3.3.3 stone:
>
> #!/bin/bash
>
> $GS_HOME/bin/startTopaz $1 -l <<EOF
>
> login
> run
> Transcript enableLoggingToGemLogFileForSession.
> Transcript show: 'wtf'.
> %
>
> commit
> logout
> exit
>
> EOF
>
>
> And then on my stone logs directory:
>
> [xx at xx logs]$ grep "wtf" *.log
> [xx at xx logs]$
>
>
> The string does gets written in the ObjectLog. But I want to gem file!
>
> Thanks in advance,
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170202/b8fbe30c/attachment.html>
More information about the Glass
mailing list