Opened 5 years ago
Last modified 5 years ago
#3969 new enhancement
Batch job instructions scattered into three different places on grass man page
Reported by: | jidanni | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | 7.8.3 |
Component: | Docs | Version: | unspecified |
Keywords: | exec batch grass.py | Cc: | |
CPU: | Unspecified | Platform: | Linux |
Description
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.
Change History (3)
comment:1 by , 5 years ago
Platform: | Unspecified → Linux |
---|
comment:2 by , 5 years ago
Keywords: | exec batch grass.py added |
---|
comment:3 by , 5 years ago
Milestone: | → 7.8.3 |
---|
(Debian linux bash)