jch wrote:
> Clever Monkey wrote:
>> jch wrote:
>>> After i figured out that i should be using release 3.6 to do a
>>> restore job, i ran into another issue. Restore needs the /tmp
>>> directory as working storage. When i restore a large system, the
>>> /tmp directory in RAM fills up instantly. To solve this problem, the
>>> restore man page says to set environment variable
>>> TMPDIR=/some_large_mounted_directory. Fine. When i do this, the
>>> restore does not recognise the environment variable properly, and the
>>> restore fails as /tmp fills up. Yet, it shows up as set when i ask
>>> for it via "set". Is this a known problem?
>>>
>> If the restore process is a subshell, you might have to export that
>> variable.
>
> Of course. I keep forgetting to issue the export command! One should
> always do it for good measure after setting an environment variable.

Typically, I'll decided what variables need to be exported to subshells,
and group those together so it is clear what I am doing, withing
cluttering up the subshell environment with garbage.

e.g.:

VAR1=foo
VAR2=bar
LOCALTMP="something local"
BLAH=Arrgh

export VAR1 VAR2 BLAH
--
clvrmnky <mailto:spamtrap@clevermonkey.org>

Direct replies will be blacklisted. Replace "spamtrap" with my name to
contact me directly.