Sponsored Content
Operating Systems Solaris NFS mount. Nobody Nobody permissions. Post 302239738 by gwhelan on Wednesday 24th of September 2008 10:40:34 AM
Old 09-24-2008
NFS mount. Nobody Nobody permissions.

Hi,

I have an NFS mount on a Solaris 10 server with file permissions nobody:nobody. This is an NFS export from an Netapp filer. Export attributes from the filer are below.

Anonymous User ID=0
Read-Write Access (All Hosts)
Security (sys)

I have other NFS exports set up with the same attributes and there is no problem with them.

Is there something I need to change on the server side to be able to change these permissions? Please helpSmilie

Thanks in advance.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

nfs permissions

Hi all can someone tell me how to set the follwoing permissions in the /etc/exports file to share a directory. I need 2 users eg a+b to be able to read and write to the directory but everyone else to just read. we have NIS in our environment and I though I could use netgroups do do this. My... (2 Replies)
Discussion started by: silvaman
2 Replies

2. 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

3. UNIX for Dummies Questions & Answers

mount -o llock -F nfs vs mount -F nfs

Hi, We encountered NFS issue (solaris) especially running on Oracle application. Problem such as forms hang when close button is click, concurrent job shows running status all time. Understand we need to use mount -o llock -F nfs instead of mount -F nfs to eliminate? this problem.. Can... (1 Reply)
Discussion started by: KhawHL
1 Replies

4. Solaris

Permissions on NFS mount

I am mounting a directory remotely but I am not able to write to the NFS mount. I am using the following commands to share and mount the file system: On source server in DFStab file share -F nfs -o rw -d "IWStore" /iw-store On the client I am mounting like this: mount -F nfs -o rw... (4 Replies)
Discussion started by: wstclair
4 Replies

5. AIX

NFS mounts and user permissions

We need to allow ordinary users to preform NFS mounts on a AIX server without giving them root access to the server. Is there a way to give an ordinary users root access on a tem basis or a script to allow them to preform NFS mounts? (4 Replies)
Discussion started by: daveisme
4 Replies

6. IP Networking

Can't see home folder on one NFS mount but can in another mount on another share

Hello, I have a few Ubuntu 9.10 laptops I'm trying to learn NFS sharing with. I am just experimenting on this right now, so no harsh words about the security of what I'm playing with, please ;) Below are the configs /etc/exports on host /home/woodnt/Homeschool... (2 Replies)
Discussion started by: Narnie
2 Replies

7. Solaris

NFS Mount permissions weird

Hi all. I have a nas mounted on a solaris box as /u04. Currently I am getting a permission denied error from my HP DataProtector backup and when I ls -l the actual directory I get: drwxrwxrwt 5 65535 nogroup 4096 Nov 9 13:46 u04 I also have SAN mounted as /u06 and it is... (1 Reply)
Discussion started by: jamie_collins
1 Replies

8. Shell Programming and Scripting

Issue with changing the permissions on an nfs mount

Hi All, I have an nfs share which I mounted to my linux machine as below. df -k output TSDapp-na-02:/vol/tsd_app_1/rn_jira 47185920 11663072 35522848 25% /opt/rn_jira I have no entry for this in my /etc/fstab. I did it by the following way. mount -t nfs... (2 Replies)
Discussion started by: Tuxidow
2 Replies

9. UNIX for Dummies Questions & Answers

Permissions for NFS share

Hi, I have created a NFS share in Solaris 10 server1 and mounted it on solaris 10 server 2.But I want to change owner of the files from nobody to a particular user in client. Which command should I use. I have tried the following but it doesn't allow to change permissions in the server2 as... (0 Replies)
Discussion started by: Rossdba
0 Replies

10. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies
NetApp::Filer::Export(3pm)				User Contributed Perl Documentation				NetApp::Filer::Export(3pm)

NAME
NetApp::Filer::Export -- OO Class for representing NFS exports SYNOPSIS
use NetApp::Filer; my $filer = NetApp::Filer->new({ ... }); # Filer methods for querying exports: my @exports = $filer->get_exports; my @temporary_exports = $filer->get_temporary_exports; my @permanent_exports = $filer->get_permanent_exports; my @active_exports = $filer->get_active_exports; my @inactive_exports = $filer->get_inactive_exports; # Methods for accessing export attributes foreach my $export ( @exports ) { } # Methods for changing export attributes DESCRIPTION
This class encapsulates a single NFS export on a NetApp filer, and provides methods for managing them. There are related methods in the NetApp::Filer class for manging exports as a whole, but the methods in this class are specific to a single NFS export. API specific attributes This API also attempts to bring some sanity to how exports are managed, and some consistency to the interface. Most of the attributes of an export are fairly obvious, and they map directly to the options supported by "exportfs" and the /etc/exports file. This API introduces two new attributes: 'type' and 'active'; The type attribute In order to distinguish between exports which are temporary (i.e. NOT saved to /etc/exports) and those which are permanent (i.e. ARE saved to /etc/exports), this API support a "type", which be either of: permanent temporary A temporary export is one which was created using "exportfs -io", and which was not saved to /etc/exports. These exports will not survive a reboot of the filer. A permanent export is one which is found in /etc/exports. The active attribute Since you can change the export options for a filesystem temporarily (for example, by using the "fencing" option -b, or just manually specifying different options and re-exporting using -io), some permanent exports may not be in effect on the system. The active attribute is used to track these. If the active attribute is true, then the export is currently in effect. Almost by definition, all temporary exports are always active. However, if a permanent export is not in effect because a temporary export for the same pathname has been created, then such an export is considerd inactive. Global vs. Limited ro/rw Attributes The "ro" and "rw" export options really have two different modes of use. If either option is specified with no "=a[:b[:c...]]" list, then it means ALL hosts. Since this API provides methods for adding and removing entries from those lists, it treats the "all" cases special, by managing thenm as separate attributes. To specify global readonly or readwrite access, use the following options: ro_all rw_all These have boolean values. The "rw" and "ro" attributes/options are ARRAY references, each containing the list of entries for an "rw=" or "ro=" list for managing limited access. Change and Update Semantics There are several methods for changing the attributes of an export object, but in ALL cases, these merely change the object in memory. In order for the attribute change to take effect, the update method must be called, which will generate and execute the appropriate "exportfs" command. For example, suppose you wanted to remove root access for a specific hostname from all exports on a filer: my $untrusted = 'unsafe.foo.com'; my @exports = $filer->get_exports; foreach my $export ( @exports ) { if ( $export->has_root( $untrusted ) ) { $export->remove_root( $untrusted ); $export->update; } } The "remove_root" method simply removes the entry from the object in memory. The "update" method re-exports that filesystem to make the change take effect on the filer. METHODS
get_filer Returns the NetApp::Filer object for the filer on which this export exists. get_type Returns a string with one of the following values: temporary permanent indicating whether or not this particular export has been written to /etc/exports. get_active Returns a boolean value, false only if the type is "permanent", and the same export was not found in the list of currently active exports (i.e. not found in the output of "exportfs"). A temporary export is always active, by definition. get_path Returns a string representing the path for the export. Note that this may not necessarily be the same as the actual pathname of the underlying volume or qtree. get_actual Returns a string representing the "actual" path of the underlying volume or qtree for the export. If a volume or qtree as been exported using a different name, this is the actual path of the underlying object. If this export option was not used, this method will return an empty string. get_nosuid Returns a boolean value, indicating whether or not the "nosuid" option is used by the export. set_nosuid( $boolean ) This method takes a single argument, interpreted in boolean context, an sets the "nosuid" option for the export. get_anon Returns the value of the "anon" option, if set. Since this option can have the value of "0", it returns undef when this option has not been set. WARNING: be careful interpreting this in a simple boolean context. To test whether or not this option has been set use "defined". set_anon( $anon ) Takes a single argument, and sest the "anon" opton to that value. To unset this option, pass an undefined value: $export->set_anon( undef ); get_sec Returns a list of the "sec" option values. set_sec( $arrayref ) Takes a single argument, an array reference of "sec" values, which can be any of: none, sec, krb5, krb5i, or krb5p. This API does no validation of these values, so if an invalid value is given, this will result in a fatal exception when the "update" method is called. has_sec( $sec ) Takes a single string argument, and returns true if that value is found in the list of "sec" options, false otherwise. add_sec( $sec ) Takes a single string argument, and adds that value to the list of "sec" options, if not already present. remove_sec( $sec ) Takes a single string argument, and removes that value from the list of "sec" options, if present. get_root Returns a list of the "root" option values. set_root( $arrayref ) Takes a single argument, an array reference of "root" values, which can be any combination of hostnames, IP addresses, or networks. Again, no data validation is performed, so bogus values will not be detected until the export is updated on the filer, using the "update" method. To clear the root option entirely, simply pass an empty array reference. has_root( $root ) Takes a single string argument, and returns true if that value is found in the list of "root" options, false otherwise. add_root( $root ) Takes a single string argument, and adds that value to the list of "root" options, if not already present. remove_root( $root ) Takes a single string argument, and removes that value from the list of "root" options, if present. get_ro_all Returns a boolean value, indicating whether or not the "ro_all" option has been set. set_ro_all( $boolean ) Takes a single boolean argument, and sets the "ro_all" option to it's value. Setting "ro_all" to a true value will clear the "ro" list, if it exists. Also, if "ro_all" is true, then the following methods will quietly do nothing: has_ro add_ro remove_ro The "ro_all" option must be cleared (set to a false value) first. get_ro Returns a list of the "ro" entries, if any. Returns nothing if "ro_all" has been set. set_ro( $arrayref ) Takes a single argument, an array reference of "ro" values. Setting the "ro" list explicitly will set clear "ro_all" (set it to a false value). has_ro( $ro ) Takes a single argument, and returns true if that value is found in the list of "ro" options, false otherwise. If "ro_all" is true, then it always returns false. add_ro( $ro ) Takes a single string argument, and adds that value to the list of "ro" options, if not already present. If "ro_all" is true, then this method will do nothing. remove_ro( $ro ) Takes a single string argument, and removes that value from the list of "ro" options, if present. If "ro_all" is true, then this method does nothing. get_rw_all, set_rw_all, get_rw, set_rw, has_rw, add_rw, remove_rw All of these methods behave exactly the same as their "ro" counterparts described immediately above. They apply to the "rw" option, instead of "ro", but if that isn't obvious... update This method re-exports the export, using "exportfs". If ANY of the object attributes have been changed programmatically, those changes will not take effect on the filer until this method has been called. Note that updating an export will not necessarily change it's "type" from temporary to permanent, unless the "type" is explicitly changed. compare( $export ) This method takes a single NetApp::Filer::Export object, and compares the current object (that is, the one on which the method was called) to it. If they have the same basic export options, it returns true, otherwise, it returns false. Only the following options are compared: actual nosuid anon sec root rw/rw_all ro/ro_all perl v5.14.2 2008-11-26 NetApp::Filer::Export(3pm)
All times are GMT -4. The time now is 06:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy