UID/GID Mapping: Difference between revisions
Jump to navigation
Jump to search
m (→Introduction: reference projids) |
mNo edit summary |
||
| Line 7: | Line 7: | ||
* You need to prevent UID, GID, and PROJID collisions between clients in different administrative domains | * You need to prevent UID, GID, and PROJID collisions between clients in different administrative domains | ||
* Two or more partner organizations would like to share data | * Two or more partner organizations would like to share data in the same filesystem | ||
* You can limit access from a partner site | * You can limit access from a partner site | ||
* You can limit administrator/root access to the filesystem | |||
== Resources == | == Resources == | ||
Revision as of 17:29, 5 March 2023
Introduction
Using Nodemap, UIDs, GIDs and PROJIDs provided by remote clients can be mapped onto a local set of UIDs, GIDs and PROJIDs.
You may find this useful if:
- You need to prevent UID, GID, and PROJID collisions between clients in different administrative domains
- Two or more partner organizations would like to share data in the same filesystem
- You can limit access from a partner site
- You can limit administrator/root access to the filesystem