[GRASS-dev] [GRASS GIS] #3969: Batch job instructions scattered into three different places on grass man page
GRASS GIS
trac at osgeo.org
Sun Nov 17 10:24:52 PST 2019
#3969: Batch job instructions scattered into three different places on grass man
page
-------------------------+-------------------------
Reporter: jidanni | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: Docs | Version: unspecified
Keywords: | CPU: Unspecified
Platform: Unspecified |
-------------------------+-------------------------
On https://grass.osgeo.org/grass79/manuals/grass7.html we observe
Running non-interactive batch jobs
If the GRASS_BATCH_JOB environment variable is set to the full path
and filename of a shell script then GRASS will be launched in a non-
interactive way and the script will be run. The script itself can be
interactive if
that is what the user requires. When it is finished GRASS will
automatically exit using the exit-success code given by the script. The
script file must have its executable bit set.
Then much farther below,
Troubleshooting
Importantly, to avoid an "[Errno 8] Exec format error" there must
be a shebang line at the top of the script (like #!/bin/sh, #!/bin/bash,
or #!/usr/bin/env python3) indicating which interpreter to be used for the
script.
The script file must have its executable bit set.
Actually they need to be combined, or at least adjacent. BTW, I found
I did not need the shebang.
In fact at a third location, far between them, one also finds a section:
Batch jobs with the exec interface
Perhaps consider combining all these three batch related sections into
one.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3969>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list