Glynn:
Actually, I really think that any advanced use (and I think that
includes running batch jobs on a cluster) should just bypass Init.sh
altogether and set the environment variables itself.
FWIW grass64 -c and GRASS_BATCH_JOB work nicely, the overhead is pretty
small. I am fine with people
Hamish wrote:
[That is in a script sourced from my ~/.bash_profile; the only time
Init.sh ever gets run here is if I'm testing changes to Init.sh.]
don't forget to run $GISBASE/etc/clean_temp every now and then to clear
out left over files from processes that die or are terminated before
On Thu, Aug 28, 2008 at 1:10 AM, Glynn Clements
[EMAIL PROTECTED] wrote:
Markus Neteler wrote:
I would like to submit the following change to facilitate the use
of GRASS on clusters/in parallel jobs:
Index: lib/init/init.sh
Markus Neteler wrote:
I would like to submit the following change to facilitate the use
of GRASS on clusters/in parallel jobs:
Index: lib/init/init.sh
===
--- lib/init/init.sh(revision 33097)
+++
I would like to submit the following change to facilitate the use
of GRASS on clusters/in parallel jobs:
Index: lib/init/init.sh
===
--- lib/init/init.sh(revision 33097)
+++ lib/init/init.sh(working copy)
@@ -159,7 +159,11
Markus Neteler wrote:
I would like to submit the following change to facilitate the use
of GRASS on clusters/in parallel jobs:
Index: lib/init/init.sh
===
--- lib/init/init.sh(revision 33097)
+++ lib/init/init.sh
On Wed, Aug 27, 2008 at 7:48 PM, Glynn Clements
[EMAIL PROTECTED] wrote:
Markus Neteler wrote:
I would like to submit the following change to facilitate the use
of GRASS on clusters/in parallel jobs:
Index: lib/init/init.sh
Markus Neteler wrote:
I would like to submit the following change to facilitate the use
of GRASS on clusters/in parallel jobs:
Index: lib/init/init.sh
===
--- lib/init/init.sh(revision 33097)
+++ lib/init/init.sh
