[GRASS-user] ignoring .gislock and consequences?

[Glynn Clements]

Jonathan Greenberg wrote:

> I recall some time ago there was a way to "hack" grass (is this a more
> formal boot-time option now?) and have it ignore .gislock to run concurrent
> processes in the same mapset.  I'm curious if this is still
possible,

The easiest way to get around the locking is to delete the .gislock
file.

> and, if so, if it would be safe to do this with multiple r.mapcalc
> runs which use different input files and different output names?

This case should be safe.

-- 
Glynn Clements <glynn at gclements.plus.com>