g.access.html 1.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. <h2>DESCRIPTION</h2>
  2. This program allows the user to control access to the
  3. current mapset. Normally, any user can read data from any
  4. GRASS mapset. But sometimes it is desirable to prohibit
  5. access to certain sensitive data. The <em>g.access</em>
  6. command allows a user to restrict read and execute access
  7. to the current mapset (see UNIX <em>chmod</em> command).
  8. <em>g.access</em> will not modify write access to the
  9. current mapset.
  10. <p>
  11. The user may, for example, allow only users in the same
  12. UNIX group to read data files in the mapset, or restrict
  13. the mapset to personal use only.
  14. <h2>NOTES</h2>
  15. <p> Under GRASS, access to the mapset PERMANENT must be open to
  16. all users. This is because GRASS looks for the user's default geographic
  17. region definition settings and the location TITLE in files that are stored
  18. under the PERMANENT mapset directory. The <em>g.access</em> command,
  19. therefore, will not allow you to restrict access to the PERMANENT mapset.
  20. <p>The <em><a href="g.mapsets.html">g.mapsets</a></em> command isn't smart
  21. enough to tell if access to a specified mapset is restricted, and the user
  22. is therefore allowed to include the names of restricted mapsets in his
  23. search path. However, the data in a restricted mapset is still protected;
  24. any attempts to look for or use data in a restricted mapset will fail. The
  25. user will simply not see any data listed for a restricted mapset.
  26. <h2>SEE ALSO</h2>
  27. UNIX manual entries for <em>chmod</em> and <em>group</em>
  28. <br>
  29. <em><a href="g.mapsets.html">g.mapsets</a></em>
  30. <h2>AUTHOR</h2>
  31. Michael Shapiro,
  32. U.S. Army Construction Engineering Research Laboratory
  33. <p><i>Last changed: $Date$</i>