inadvertantly used private email ... I think that my response may
contain generally useful information...
-------- Forwarded Message --------
I've been pre-ocuppied with Rowan work and taking care of my
wife and grand kids ... My wife spent a couple of weeks in the
hospital back in February and while she has been getting better
every day, she's still not all the way back and it may take a
few more months before she's back to normal, so my email queue
has been backing up ...
I appreciate the fact that you pinged me ...
My answers are embedded below ...
On 03/16/2018 12:21 PM, Ken Treis wrote:
Dale,Well it is not directly asking for trouble, but the full tODE implementation is dependent upon directory structure and a set of environment variables that reference key points in the directory structure ... so the issues you are seeing are more than likely caused by one or more of the environment variables used by GsDevKit_home and tODE not being correctly set or pointing at chunks of the directory structure that are not present ...
Frankly it was hard enough to put together the set of scripts and directory structure in the first place, without trying to wrap my head around trying to figure out how to help you figure out which pieces of the infrastructure you cannot live without ...
I'm afraid that trying to get tODE to be fully functional outside the environment it was designed to work within, could turn out to be a slow process of re-creating the GsDevKit_home environment within the context of your structure and scripts.
OTOH, you might be one env var away from success... so I'll go ahead and start the process of trying to help you get things working ...
If you run `$GS_HOME/bin/utils/gsDevKitEnvVars` you will see that there are about 80 environment variables that are defined by GsDevKit_home (I've listed the set of env var values that are set for my environment in the attached file). As I scan the list it seems to me that most of those env vars are likely to be used at one point or another while using tODE ...
... but that's not all. It is not quite enough to just install the tODE code into your stone. There are a set of tODE scripts that are also run after tODE is installed to create a directory structure. The code that creates the directory structure is implemented in the Pharo devKitCommandLine image and is triggered by running the todeLoad script ... so in theory, the whole sequence of steps can be reverse engineered, but teasing out the bits that you need to run so that you can install tODE in your environment will be very tedious ...
As I spend the time to think about your "problem". I think that you would be better off install tODE into your stone by transplanting your extents into a GsDevKit_home installation, installing tODE using the standard GsDevKit_home scripts, then moving your extents back into your old structure and then make sure that when you run tODE all of the GsDevKit_home env vars are set pointing at the GsDevKit_home/tODE directory structure under GS_HOME....
This is the sequence of steps that I think you would need to do:
# 1. Install tode into your extent (this should be the upgraded extent before you installed tODE using your process)
# When this step is done, the expected directory structure for tODE will have been created under $GS_HOME,
# but you should be able to cp the extent back into your /opt/gemstone location as long as you make sure the
# env vars are set up correctly
$GS_HOME/bin/createStone -s <path-to-your-extent-without-tode-installed> tode_stone <gs-version>
cp $GS_HOME/server/stones/tode_stone/extents/extent0.dbf <path-to-your-extent-without-tode-installed>
# 2. customize your netldi startup script to pick up the GsDevKit_home env vars
# If you look at the startNetldi script you will see the following bash code is being run
# This sequence ensures that the appropriate environment variables are defined for
# GsDevKit_home and the stone --- both of which may be used by tODE:
pushd "$stonePath" >& /dev/null
popd >& /dev/null
So at this point I am pretty optimistic that this approach will get you going ...
Glass mailing list
envvars (6K) Download Attachment
Dale, thanks for setting me on the right track here. I hope your wife's health continues to improve.
This approach looks like it's going to work, but I ran into problems with the `createStone` because my repository is too big for the default free keyfile. Is it possible to specify an alternate keyfile when invoking `createStone`?
Miriam Technologies, Inc.
(866) 652-2040 x221
Glass mailing list
|Free forum by Nabble||Edit this page|