Export a file system with write permissions


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory Export a file system with write permissions
# 8  
Old 05-27-2008
I don't think ZFS will do anything for you, the permissions are handled by NFS.
In the manpage exports, there is a section (looking at the linux manpage) about user id mapping. When you have the same userid's on both hosts. The permissions are inherited from the server to the client (that is at least possible, may differ on different OS-es)
So when you have the permissions right on the server (user2 rw, rest ro) you will have the same rights on the client.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to give permissions to read write but not delete the file?

i want to give users the ability to create write and read files in other user directory , but not to have option to delete the file after created ( sticky bit not going to work here ... ) for example : i have user : manager with directory repository i have user : worker1 that need to write... (4 Replies)
Discussion started by: umen
4 Replies

2. Red Hat

List full File system permissions

I am attempting to get a baseline of deployed RHEL 6.5 servers and need to produce a full filesystem permission settings list.....but I forgot the bloody command and am racking my brain and now have a migraine. I just need a simple list starting at "/" right down the tree, listing the folder,... (3 Replies)
Discussion started by: strykergli250hp
3 Replies

3. AIX

Write once on NFS file system

Hello Guru's We are trying to save some data for 10 -15 yrs. so we created a NFS share file system and mounted on AIX 5.3 servers, keeping in mind that we might need to replace the expired disk/bad disk every 2 yrs or 4 yrs. Now we are trying to solve. How to protect it from getting deleted... (6 Replies)
Discussion started by: Beginner123
6 Replies

4. SCO

Read and write into file system from SCO

hi Knows someone what kind of file system uses SCO Unix 5.0.6? Which linux or unix LIVE CD can read and write into file system from SCO Unix? I've tried to boot SCO using Knoppix 6.2.1 LIVE CD, but cannot mount. # mount -t sysv /dev/sda1 /mnt mount: wrong fs type, bad option, bad superblock... (2 Replies)
Discussion started by: ccc
2 Replies

5. UNIX for Dummies Questions & Answers

Creating a File system with required permissions for all DIR's created in

Hello All, I am application admin. I need to clear all the temporary files cleared by the applications. I need help/suggestion that is there any way to create a file system such that every Dir created in by any user will have 775 permissions. So, that i can simply clear the temporary file which... (6 Replies)
Discussion started by: firestar
6 Replies

6. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

7. AIX

How to export AIX File system NFS to Windows ?

Hello, Can someone please point to an easy document or steps how to export AIX file system /whatever to Windows O/S Basically Windows should see this filesystem / directory and should be able to write in this filesystem / directory Thanks (2 Replies)
Discussion started by: filosophizer
2 Replies

8. Filesystems, Disks and Memory

Is it possible to re-export a exported NFS file system?

Hi... Is it possible to re-export a exported NFS file system? If no, Why? Let me know, if any further details are required about the question. Thanks in advance Adams:) (5 Replies)
Discussion started by: Adams Nave
5 Replies

9. HP-UX

nfs export permissions

Hello, If I have an export like: /usr/temp -rw=ram:alligator means that /usr/temp has "rw" permissions to ram and alligator machines and has "ro" to everyone else? (1 Reply)
Discussion started by: psimoes79
1 Replies

10. Shell Programming and Scripting

Write system variables into file

Hi everyone, I was told, i my job, to do a script that creates the backup of all the files that are important to us. So i created the script, put it in the crontab and it works great. Now what i want is to write to a file what directories have being copied with date and time. How can i... (3 Replies)
Discussion started by: jorge.ferreira
3 Replies
Login or Register to Ask a Question
rsm_memseg_export_publish(3RSM) 		      Remote Shared Memory Library Functions			   rsm_memseg_export_publish(3RSM)

NAME
rsm_memseg_export_publish, rsm_memseg_export_unpublish, rsm_memseg_export_republish - allow or disallow a memory segment to be imported by other nodes SYNOPSIS
cc [ flag... ] file... -lrsm [ library... ] #include <rsmapi.h> int rsm_memseg_export_publish(rsm_memseg_export_handle_t memseg, rsm_memseg_id_t *segment_id, rsmapi_access_entry_t access_list[], uint_t access_list_length); int rsm_memseg_export_unpublish(rsm_memseg_export_handle_t memseg); int rsm_memseg_export_republish(rsm_memseg_export_handle_t memseg, rsmapi_access_entry_t access_list[], uint_t access_list_length); DESCRIPTION
The rsm_memseg_export_publish(), rsm_memseg_export_unpublish(), and rsm_memseg_export_republish() functions allow or disallow a memory seg- ment to be imported by other nodes. The rsm_memseg_export_publish(3RSM) function allows the export segment specified by the memseg argument to be imported by other nodes. It also assigns a unique segment identifier to the segment and defines the access control list for the segment. The segment_id argument is a pointer to an identifier which is unique on the publishing node. It is the responsibility of the application to manage the assignment of unique segment identifiers. The identifier can be optionally initialized to 0, in which case the system will return a unique segment iden- tifier value. The access_list argument is composed of pairs of nodeid and access permissions. For each nodeid specified in the list, the associated read/write permissions are provided by three octal digits for owner, group, and other, as for Solaris file permissions. In the access control each octal digit may have the following values: 2 write access 4 read only access 6 read and write access An access permissions value of 0624 specifies:(1) an importer with the same uid as the exporter has read and write access; (2) an importer with the same gid as the exporter has write access only; and(3) all other importers have read access only. When an access control list is provided, nodes not included in the list will be prevented from importing the segment. However, if the access list is NULL (this will require the length access_list_length to be specified as 0 as well), then no nodes will be excluded from importing and the access permis- sions on all nodes will equal the owner-group-other file creation permissions of the exporting process. Corresponding to the access_list argument, the access_list_length argument specifies the number of entries in the access_list array. The rsm_memseg_export_unpublish() function disallows the export segment specified by memseg from being imported. All the existing import connections are forcibly disconnected. The rsm_memseg_export_republish() function changes the access control list for the exported and published segment. Although the current import connections remain unaffected by this call, new connections are constrained by the new access list. RETURN VALUES
Upon successful completion, these functions return 0. Otherwise, an error value is returned to indicate the error. ERRORS
The rsm_memseg_export_publish(), rsm_memseg_export_unpublish(), and rsm_memseg_export_republish() functions can return the following errors: RSMERR_BAD_SEG_HNDL Invalid segment handle. RSMERR_NOT_CREATOR Not creator of segment. The rsm_memseg_export_publish() and rsm_memseg_export_republish() functions can return the following errors, with the exception that only rsm_memseg_export_publish() can return the errors related to the segment identifier: RSMERR_SEGID_IN_USE Segment identifier in use. RSMERR_RESERVED_SEGID Segment identifier reserved. RSMERR_BAD_SEGID Invalid segment identifier. RSMERR_BAD_ACL Invalid access control list. RSMERR_SEG_ALREADY_PUBLISHED Segment already published. RSMERR_INSUFFICIENT_MEM Insufficient memory. RSMERR_INSUFFICIENT_RESOURCES Insufficient resources. RSMERR_LOCKS_NOT_SUPPORTED Locks not supported. RSMERR_BAD_ADDR Bad address. The rsm_memseg_export_republish() and rsm_memseg_export_unpublish() functions can return the following errors: RSMERR_SEG_NOT_PUBLISHED Segment not published. RSMERR_INTERRUPTED The operation was interrupted by a signal. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
rsm_memseg_export_create(3RSM), attributes(5) NOTES
An attempt to publish a segment might block until sufficient resources become available. SunOS 5.10 8 Jun 2001 rsm_memseg_export_publish(3RSM)