Opened 5 years ago
Last modified 5 years ago
#3963 new enhancement
Document turning off progress messages on batch jobs
| Reported by: | jidanni | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.8.3 |
| Component: | Python | Version: | git-releasebranch78 |
| Keywords: | grass.py exec batch quiet | Cc: | |
| CPU: | Unspecified | Platform: | Unspecified |
Description
On https://grass.osgeo.org/grass79/manuals/grass7.html , regarding running batch jobs, it needs to be mentioned how to suppress these six verbose lines,
$ grass --exec true 2>&1 | nl
1 Starting GRASS GIS...
2 Cleaning up temporary files...
3 Executing <true> ...
4 Execution of <true> finished.
5 Cleaning up default sqlite database ...
6 Cleaning up temporary files...
in order to have a clean running batch job, (e.g., one that could be run by cron without sending the user an email message due to errors.)
Alas, the grass man page does not list a --quiet option.
Sure, the man page could simply say to use 2>&- or 2>/dev/null, but that would also wipe out real error messages.
Change History (4)
comment:1 by , 5 years ago
| Component: | Docs → Python |
|---|---|
| Keywords: | grass.py added |
| Milestone: | → 7.8.2 |
| Priority: | trivial → normal |
| Version: | unspecified → git-releasebranch78 |
comment:2 by , 5 years ago
| Keywords: | exec batch quiet added |
|---|
comment:4 by , 5 years ago
| Milestone: | → 7.8.3 |
|---|
Note:
See TracTickets
for help on using tickets.

Yes, a
--quietflag would be great for thegrass7xstart script.