[Glass] Fwd: Who is overriding $GEMSTONE_LOGDIR ?

Dale Henrichs via Glass glass at lists.gemtalksystems.com
Fri Oct 9 10:58:43 PDT 2015


This one looks like it is fixed in 3.3.0

Dale

On 10/09/2015 10:15 AM, Mariano Martinez Peck wrote:
>
> On Mon, May 12, 2014 at 3:14 PM, Dale Henrichs 
> <dale.henrichs at gemtalksystems.com 
> <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>
>     Mariano,
>
>     Good catch. I've submitted internal bug #44216 so that we can get
>     this patch included in the product (possibly 3.2.1) ...
>
>
> Hi Dale, do you know if that issue was finally integrated? Because I 
> still see 3.2.9 misc.sh doing:
>
> GEMSTONE_LOGDIR="$GEMSTONE_LOCKBASE/log"          # required log directory
>
> thanks
>
>     Dale
>
>
>     On Mon, May 12, 2014 at 9:47 AM, Mariano Martinez Peck
>     <marianopeck at gmail.com <mailto:marianopeck at gmail.com>> wrote:
>
>         Hi guys,
>
>         I am reviving this old thread because I found the problem. I
>         do use the /product/seaside/bin scripts, like
>         startSeasideGem30 etc... However, I have my own env SET for
>         each stone I have and for each I define the set of variables.
>         All were working correctly but GEMSTONE_LOGDIR. The problem
>         was the  /opt/gemstone/product/bin/misc.sh  does this at the
>         very beginning:
>
>         GEMSTONE_LOGDIR="$GEMSTONE_LOCKBASE/log"
>
>         So it directly sets the GEMSTONE_LOGDIR even if it could have
>         been already set. What I did as a workaround is:
>
>         if [ -n "$GEMSTONE_LOGDIR" ]; then
>         GEMSTONE_LOGDIR="$GEMSTONE_LOCKBASE/log"          #   required
>         log directory
>
>         Now /product/seaside/bin  scripts get the correct GEMSTONE_LOGDIR.
>
>         Best,
>
>
>
>
>         On Wed, Jan 15, 2014 at 8:54 PM, Dale Henrichs
>         <dale.henrichs at gemtalksystems.com
>         <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>
>             new mailer and replied to sender instead of list ...
>
>             ---------- Forwarded message ----------
>             From: *Dale Henrichs* <dale.henrichs at gemtalksystems.com
>             <mailto:dale.henrichs at gemtalksystems.com>>
>             Date: Wed, Jan 15, 2014 at 10:40 AM
>             Subject: Re: [Glass] Who is overriding $GEMSTONE_LOGDIR ?
>             To: Mariano Martinez Peck <marianopeck at gmail.com
>             <mailto:marianopeck at gmail.com>>
>
>
>             gemnetobject15083MacBook-Pro-de-Mariano.local.log is the
>             log file for an rpc gem and is constructed with gem pid
>             and the name of your machine (preumably
>             MacBook-Pro-de-Mariano.local).
>
>             It shows up in your home directory when you have _NOT_
>             set GEMSTONE_LOGDIR.
>
>             The ones on your mac are from gems started against the
>             stone running on your mac and therefore the netldi that is
>             running on your mac may not have had the correct env vars
>             set before it was started
>
>             Dale
>
>
>             On Tue, Jan 14, 2014 at 11:56 AM, Mariano Martinez Peck
>             <marianopeck at gmail.com <mailto:marianopeck at gmail.com>> wrote:
>
>                 mmmmm I have a related problem.... I don't know why
>                 the log of my gems are written with a name like
>                 'gemnetobject15083MacBook-Pro-de-Mariano.local.log'
>                 and they are being written into my $HOME
>                 folder.....weird. There is clearly something wrong
>                 with the log variables or parameters.
>                 I will try to find what is going on...
>
>                 Thanks,
>
>
>
>
>                 On Tue, Jan 14, 2014 at 4:01 PM, Mariano Martinez Peck
>                 <marianopeck at gmail.com <mailto:marianopeck at gmail.com>>
>                 wrote:
>
>
>
>
>                     On Tue, Jan 14, 2014 at 3:07 PM, Bill Erickson
>                     <bill.erickson at gemtalksystems.com
>                     <mailto:bill.erickson at gemtalksystems.com>> wrote:
>
>                         Mariano,
>
>                         If you're using RPC topaz, remember that the
>                         netldi spawns the gem process using the
>                         environment that was in effect at the time
>                         netldi was started. If you change anything in
>                         this environment, you need to shutdown and
>                         restart netldi in order for any gems spawned
>                         by the netldi to include the updated variables.
>
>
>                     Hi Bill,
>
>                     Thanks for the answer. Good point. I have
>                     restarted the netldi just in case but same
>                     problem. I made sure that the variables are
>                     correctly exported when I started netldi and they
>                     were...
>                     So I might have a problem elsewhere.... :(
>
>
>                         ------------------------------------------------------------------------
>                         Bill Erickson
>                         GemTalk Systems Engineering
>                         15220 NW Greenbrier Parkway #240, Beaverton OR
>                         97006
>                         ------------------------------------------------------------------------
>
>
>                             Mariano Martinez Peck wrote
>                             > ... I am getting the incorrect result with
>                             >  $GEMSTONE_LOGDIR. For some reason, no
>                             matter I have set/exported the
>                             > variable to my own value, like
>                             /opt/applications/test2/gemstone/log, I
>                             > always get '/opt/gemstone/log'.
>
>                             View this message in context:
>                             http://forum.world.st/Glass-Who-is-overriding-GEMSTONE-LOGDIR-tp4736718p4736723.html
>                             Sent from the GLASS mailing list archive
>                             at Nabble.com.
>                             _______________________________________________
>                             Glass mailing list
>                             Glass at lists.gemtalksystems.com
>                             <mailto:Glass at lists.gemtalksystems.com>
>                             http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
>                         _______________________________________________
>                         Glass mailing list
>                         Glass at lists.gemtalksystems.com
>                         <mailto:Glass at lists.gemtalksystems.com>
>                         http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
>
>                     -- 
>                     Mariano
>                     http://marianopeck.wordpress.com
>
>
>
>
>                 -- 
>                 Mariano
>                 http://marianopeck.wordpress.com
>
>                 _______________________________________________
>                 Glass mailing list
>                 Glass at lists.gemtalksystems.com
>                 <mailto:Glass at lists.gemtalksystems.com>
>                 http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
>
>             _______________________________________________
>             Glass mailing list
>             Glass at lists.gemtalksystems.com
>             <mailto:Glass at lists.gemtalksystems.com>
>             http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
>
>         -- 
>         Mariano
>         http://marianopeck.wordpress.com
>
>
>
>
>
> -- 
> Mariano
> http://marianopeck.wordpress.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20151009/078d9d37/attachment-0001.html>


More information about the Glass mailing list