Opened 13 months ago

Last modified 12 months ago

#3969 new enhancement

Batch job instructions scattered into three different places on grass man page

Reported by: jidanni Owned by: grass-dev@…
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 Changed 13 months ago by jidanni

Platform: UnspecifiedLinux

(Debian linux bash)

comment:2 Changed 12 months ago by wenzeslaus

Keywords: exec batch grass.py added

comment:3 Changed 12 months ago by neteler

Milestone: 7.8.3
Note: See TracTickets for help on using tickets.