-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ydb_env_set preserves ydb_gbldir/gtmgbldir and ydb_routines/gtmroutines #197
Comments
Is the intention is to have the script NOT modify $ydb_gbldir and $ydb_routines/$gtmroutines (so after the script runs they are the same values they were before the script ran? |
Yes, if they are set going in, then leave them unchanged. If they are
not set, then set them to the defaults.
– Bhaskar
…On 05/07/2018 11:36 AM, Christopher Edwards wrote:
Is the intention is to have the script NOT modify $ydb_gbldir and
$ydb_routines/$gtmroutines (so after the script runs they are the same
values they were before the script ran?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#197 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAiqesBXKIUhHcyb5EHFqi-KjbTssPNwks5twGn4gaJpZM4TNA7J>.
--
YottaDB - Rock solid. Lightning fast. Secure. Pick any three.
|
The original idea was that if $ydb_gbldir and $ydb_routines had a
pattern matching $ydb_rel from another release, or $gtmver from a GT.M
version, that ydb_env_set would replace the pattern with $ydb_rel for
the current release. If you can do that reliably, then I think it's
worth doing it. Otherwise, make the simplistic fix below.
– Bhaskar
…On 05/07/2018 11:38 AM, K.S. Bhaskar wrote:
Yes, if they are set going in, then leave them unchanged. If they are
not set, then set them to the defaults.
– Bhaskar
On 05/07/2018 11:36 AM, Christopher Edwards wrote:
>
> Is the intention is to have the script NOT modify $ydb_gbldir and
> $ydb_routines/$gtmroutines (so after the script runs they are the
> same values they were before the script ran?
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <#197 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAiqesBXKIUhHcyb5EHFqi-KjbTssPNwks5twGn4gaJpZM4TNA7J>.
>
--
YottaDB - Rock solid. Lightning fast. Secure. Pick any three.
--
YottaDB - Rock solid. Lightning fast. Secure. Pick any three.
|
Thanks! |
Pull request #238 resolves this and is merged. |
nars1
added a commit
to nars1/YottaDB
that referenced
this issue
May 8, 2018
… if needs a preceding semicolon) Before this fix, the following error used to show up if one sourced ydb_env_set $ . ydb_env_set sh: 82: ydb_env_set: Syntax error: end of file unexpected (expecting "fi")
nars1
added a commit
that referenced
this issue
May 8, 2018
…ds a preceding semicolon) Before this fix, the following error used to show up if one sourced ydb_env_set $ . ydb_env_set sh: 82: ydb_env_set: Syntax error: end of file unexpected (expecting "fi")
ksbhaskar
changed the title
ydb_env_set overrides ydb_routines/gtmroutines environment variables
ydb_env_set preserves ydb_gbldir/gtmgbldir and ydb_routines/gtmroutines
May 8, 2018
nars1
added a commit
to nars1/YottaDB
that referenced
this issue
May 16, 2018
… to not be correctly set after ydb_env_set Simple test case that illustrates the problem with the current mainline. $ . /usr/local/lib/yottadb/r122/ydb_env_set $ env | grep ydb_routines ydb_routines=/usr/local/lib/yottadb/r122/libyottadbutil.so But with r1.20, the same test shows ydb_routines with a lot more values and these are needed for the "ydb" script to work fine. $ . /usr/local/lib/yottadb/r120/ydb_env_set $ env | grep ydb_routines ydb_routines=/home/user/.yottadb/r1.20_x86_64/o*(/home/user/.yottadb/r1.20_x86_64/r /home/user/.yottadb/r) /usr/local/lib/yottadb/r120/libyottadbutil.so With the fix, ydb_routines gets set to a value just like what it used to be in r1.20.
nars1
added a commit
that referenced
this issue
May 16, 2018
… be correctly set after ydb_env_set Simple test case that illustrates the problem with the current mainline. $ . /usr/local/lib/yottadb/r122/ydb_env_set $ env | grep ydb_routines ydb_routines=/usr/local/lib/yottadb/r122/libyottadbutil.so But with r1.20, the same test shows ydb_routines with a lot more values and these are needed for the "ydb" script to work fine. $ . /usr/local/lib/yottadb/r120/ydb_env_set $ env | grep ydb_routines ydb_routines=/home/user/.yottadb/r1.20_x86_64/o*(/home/user/.yottadb/r1.20_x86_64/r /home/user/.yottadb/r) /usr/local/lib/yottadb/r120/libyottadbutil.so With the fix, ydb_routines gets set to a value just like what it used to be in r1.20.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Final Release Note
Values of environment variables
ydb_gbldir
/gtmgbldir
andydb_routines
/gtmroutines
set before sourcingydb_env_set
are preserved. The ydb_* versions of the environment variables is used if both ydb_* and gtm* versions are defined. (#197)Description
The
ydb_env_set
command overrides any previous value set for theydb_routines
andgtmroutines
environment variable. This is a regression from thegtmprofile
file, which did not, and which the new file was intended to replace.ydb_gbldir
is also affected.Draft Release Note
ydb_gbldir/gtmgbldir and ydb_routines/gtmroutines set before running ydb_env_set are preserved. The ydb_* versions of the environment variables is used if both ydb_* and gtm* versions are defined.
The text was updated successfully, but these errors were encountered: