[Glass] Fwd: Who is overriding $GEMSTONE_LOGDIR ?

[Dale Henrichs]

new mailer and replied to sender instead of list ...

---------- Forwarded message ----------
From: Dale Henrichs <dale.henrichs at gemtalksystems.com>
Date: Wed, Jan 15, 2014 at 10:23 AM
Subject: Re: [Glass] Who is overriding $GEMSTONE_LOGDIR ?
To: Mariano Martinez Peck <marianopeck at gmail.com>


Mariano,

`source`ing defSeaside will override GEMSTONE_LOGDIR as it `source`s
$GEMSTONE/seaside/etc/gemstone.conf which as Richard has pointed is the
likely source of the override.

If your netldi is clean, then you need to track the process lineage (who
started whom by what means) as the env vars follow the process fork lineage
...

There is another env var to be aware of GEMSTONE_NRS_ALL as the following
(which I set in my .bashrc) sets the GEMSTONE_LOGDIR as well ... somewhat
indirectly:

  GEMSTONE_NRS_ALL=#dir:/opt/gemstone/log

Dale


On Tue, Jan 14, 2014 at 11:01 AM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

>
>
>
> On Tue, Jan 14, 2014 at 3:07 PM, Bill Erickson <
> 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
>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>
>>
>>
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>
>>
>
>
> --
> 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/20140115/259bf30d/attachment.html>