Glynn, Thanks, but I don't want to break that feature in GRASS. I suppose I was hoping that someone might have a suggestion as to how I might set an environment variable or do something in my script that would set the login ID to 'oper' that GRASS would recognize as legitimate. Someone I work with suggested that some use of 'expect' might work; so, I am playing with that approach.
Regards, Tom ----- Original Message ----- From: Glynn Clements <[EMAIL PROTECTED]> Date: Sunday, October 28, 2007 11:12 pm Subject: Re: [GRASS-user] Question about MAPSET permissions with a GRASS script > > Thomas Adams wrote: > > > I have written a GRASS shell script for Linux that works > perfectly well > > except for one thing. Anyone who runs it from their login ID must > be > > able to run the script, which they initiate manually. The MAPSET > is > > generic, called 'oper' � we have an 'oper' Linux login. What > happens is > > that unless I login or 'su' to 'oper', the script fails with: > > > > ERROR: MAPSET oper � permission denied > > ERROR: MAPSET oper � permission denied > > ERROR: MAPSET oper � permission denied > > . > > . > > . > > etc. > > > > The process involves (among other things) reading in point data > using > > v.in.ascii and spatially interpolating it to a raster. > > > > I have tried a number of things to set the GRASS permissions to > allow > > universal access to the 'oper' MAPSET as well as trying to export > the > > USER variable, etc. Nothing seems to work. Does anyone have a > > suggestion? > > GRASS requires that you own the current mapset. > > If you want to avoid this, you need to remove the check from > G__mapset_permissions() in lib/gis/mapset_msc.c. > > -- > Glynn Clements <[EMAIL PROTECTED]> > _______________________________________________ grassuser mailing list grassuser@grass.itc.it http://grass.itc.it/mailman/listinfo/grassuser