We wish to use GRASS 6.0/6.1 on a computer with users using different accounts. It was installed by a root user and it runs fine from that account. However, we can't seem to get a non-root user to start the program. I have created a local .grassrc6 file. Typing 'grass6' at a prompt returns something like 'command not found', and the icon start-up just quits. I assume this is something quite simple!
Many thanks.
--
Dan Gavin
Research Associate
University of Vermont
Botany and Agricultural Biochemistry
120B Marsh Life Science
109 Carrigan Dr.
Burlington, VT 05405-0086
802.656.0297
Unfortunately you must have administrative access (root) to run grass. I
haven't heard of any way around this.
-Ian
Quoting Daniel Gavin <Daniel.Gavin@uvm.edu>:
We wish to use GRASS 6.0/6.1 on a computer with users using different
accounts. It was installed by a root user and it runs fine from that
account. However, we can't seem to get a non-root user to start the
program. I have created a local .grassrc6 file. Typing 'grass6' at
a prompt returns something like 'command not found', and the icon
start-up just quits. I assume this is something quite simple!
Many thanks.
--
Dan Gavin
Research Associate
University of Vermont
Botany and Agricultural Biochemistry
120B Marsh Life Science
109 Carrigan Dr.
Burlington, VT 05405-0086
802.656.0297
-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB
"insert witticism here"
Ian W. Macmillan wrote:
Unfortunately you must have administrative access (root) to run grass. I
haven't heard of any way around this.
That definitely isn't true.
However, you need to ensure that directory ownership and permissions
are correct, e.g.:
1. A user needs to own their mapset directories; write permission
isn't sufficient (although it isn't hard to remove this restriction if
it's a problem).
2. To create a new mapset within a location, a user needs write
permission on the location directory.
3. To create a new location, a user needs write permission on the
database directory.
How to achieve this depends upon how much freedom the users need.
For a teaching environment where the users are students carrying out
predetermined tasks with a supplied dataset, root can pre-create all
of the mapset directories (one per user, plus PERMANENT) and set each
user's directory to be owned by that user.
If you need more flexibility, e.g. the users are staff, researchers or
more advanced students, and need to be able to create new locations
and mapsets, the database and location directories need to be at least
group-writable so that users can create new subdirectories.
--
Glynn Clements <glynn@gclements.plus.com>
Alas, I have shown my ignorance once again, thanks for the clarification.
-ian
Quoting Glynn Clements <glynn@gclements.plus.com>:
Ian W. Macmillan wrote:
> Unfortunately you must have administrative access (root) to run grass. I
> haven't heard of any way around this.
That definitely isn't true.
However, you need to ensure that directory ownership and permissions
are correct, e.g.:
1. A user needs to own their mapset directories; write permission
isn't sufficient (although it isn't hard to remove this restriction if
it's a problem).
2. To create a new mapset within a location, a user needs write
permission on the location directory.
3. To create a new location, a user needs write permission on the
database directory.
How to achieve this depends upon how much freedom the users need.
For a teaching environment where the users are students carrying out
predetermined tasks with a supplied dataset, root can pre-create all
of the mapset directories (one per user, plus PERMANENT) and set each
user's directory to be owned by that user.
If you need more flexibility, e.g. the users are staff, researchers or
more advanced students, and need to be able to create new locations
and mapsets, the database and location directories need to be at least
group-writable so that users can create new subdirectories.
--
Glynn Clements <glynn@gclements.plus.com>
-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB
"insert witticism here"
Thank you for this explanation. I will make a group-writeable database directory for my project (my next chance will be in a few days, though!).
At 12:08 AM +0100 5/28/05, Glynn Clements wrote:
Ian W. Macmillan wrote:
Unfortunately you must have administrative access (root) to run grass. I
haven't heard of any way around this.
That definitely isn't true.
However, you need to ensure that directory ownership and permissions
are correct, e.g.:
1. A user needs to own their mapset directories; write permission
isn't sufficient (although it isn't hard to remove this restriction if
it's a problem).
2. To create a new mapset within a location, a user needs write
permission on the location directory.
3. To create a new location, a user needs write permission on the
database directory.
How to achieve this depends upon how much freedom the users need.
For a teaching environment where the users are students carrying out
predetermined tasks with a supplied dataset, root can pre-create all
of the mapset directories (one per user, plus PERMANENT) and set each
user's directory to be owned by that user.
If you need more flexibility, e.g. the users are staff, researchers or
more advanced students, and need to be able to create new locations
and mapsets, the database and location directories need to be at least
group-writable so that users can create new subdirectories.
--
Glynn Clements <glynn@gclements.plus.com>
--
Dan Gavin
Research Associate
University of Vermont
Botany and Agricultural Biochemistry
120B Marsh Life Science
109 Carrigan Dr.
Burlington, VT 05405-0086