[GRASS5] [bug #269] (grass) Grass5 and NFS

GRASS GRASS developer
1

this bug's URL: http://intevation.de/rt/webrt?serial_num=269
-------------------------------------------------------------------------

Subject: Grass5 and NFS

Platform: Linux/Intel
Linux distro: RedHat
linux cpu: AMD (K6, ...)
Xwindows version: Xfree 4.0.x
Xwindows manager: wmaker
grass binary for platform: I compiled the sources myself
grass sources source: no, I got a source code package from the server, 5beta1
c compiler name: gcc

at the command d.mon start=x0 it asnwers that it can't complite the locking procedure.
Indeed the dir for locking is exported by nfs and it doesn't have the permision to write on it.

So maybe there is a env-variable to change in order to make grass lock at a dir with write permision.

chmod -R 1777 /usr/local/grass5/locks/

just done but nothin change.

Arjuna

-------------------------------------------- Managed by Request Tracker

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

2

Request Tracker wrote:

at the command d.mon start=x0 it asnwers that it can't complite the
locking procedure.

Indeed the dir for locking is exported by nfs and it doesn't have the
permision to write on it.

So maybe there is a env-variable to change in order to make grass lock
at a dir with write permision.

An environment variable is probably a bad idea; in order for lock
files to work, all processes have to use the same path. With an
environment variable, this may not happen.

It may be worth making it a compile-time option, though.

BTW: what is this directory used for?

--
Glynn Clements <glynn.clements@virgin.net>

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'