10 More Discussions You Might Find Interesting
1. Red Hat
RHEL 7.1 client using autofs to mount a NIS map of home directories being exported by a Solaris 10x86 nfs server.
The owner and group are correct on the NFS server, but on the RHEL client, the owner and group end up being nobody nobody. The USERS and GROUPS are NIS maps as well. They are... (2 Replies)
Discussion started by: mrmurdock
2 Replies
2. Solaris
Hi,
I have a Solaris 10 server and I want to export a filesystem to a linux client and give the client's root user root priviliges on the filesystem.
The client is an ubuntu 14.04 LTS server.
the dfstab on the server looks lik this:
/usr/sbin/share -F nfs -o ... (1 Reply)
Discussion started by: nvanvliet
1 Replies
3. UNIX for Dummies Questions & Answers
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
4. UNIX for Advanced & Expert Users
Please bare with me while I try to explain this weird problem.
We are exporting a filesystem from an aix box to two linux boxes.
On the linux box a java-weblogic application hits the share.
For explanation benefits I'll describe the users thus.
aix filesystem owned by userA in groupA
on... (2 Replies)
Discussion started by: fwellers
2 Replies
5. Shell Programming and Scripting
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
6. Solaris
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
7. AIX
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
8. Solaris
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
9. Solaris
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... (7 Replies)
Discussion started by: gwhelan
7 Replies
10. HP-UX
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
STRMODE(3) BSD Library Functions Manual STRMODE(3)
NAME
strmode -- convert inode status information into a symbolic string
LIBRARY
Utility functions from BSD systems (libbsd, -lbsd)
SYNOPSIS
#include <bsd/string.h>
void
strmode(mode_t mode, char *bp);
DESCRIPTION
The strmode() function converts a file mode (the type and permission information associated with an inode, see stat(2)) into a symbolic
string which is stored in the location referenced by bp. This stored string is eleven characters in length plus a trailing NUL.
The first character is the inode type, and will be one of the following:
- regular file
b block special
c character special
d directory
l symbolic link
p fifo
s socket
w whiteout
? unknown inode type
The next nine characters encode three sets of permissions, in three characters each. The first three characters are the permissions for the
owner of the file, the second three for the group the file belongs to, and the third for the ``other'', or default, set of users.
Permission checking is done as specifically as possible. If read permission is denied to the owner of a file in the first set of permis-
sions, the owner of the file will not be able to read the file. This is true even if the owner is in the file's group and the group permis-
sions allow reading or the ``other'' permissions allow reading.
If the first character of the three character set is an ``r'', the file is readable for that set of users; if a dash ``-'', it is not read-
able.
If the second character of the three character set is a ``w'', the file is writable for that set of users; if a dash ``-'', it is not
writable.
The third character is the first of the following characters that apply:
S If the character is part of the owner permissions and the file is not executable or the directory is not searchable by the owner, and
the set-user-id bit is set.
S If the character is part of the group permissions and the file is not executable or the directory is not searchable by the group, and
the set-group-id bit is set.
T If the character is part of the other permissions and the file is not executable or the directory is not searchable by others, and the
``sticky'' (S_ISVTX) bit is set.
s If the character is part of the owner permissions and the file is executable or the directory searchable by the owner, and the set-
user-id bit is set.
s If the character is part of the group permissions and the file is executable or the directory searchable by the group, and the set-
group-id bit is set.
t If the character is part of the other permissions and the file is executable or the directory searchable by others, and the ``sticky''
(S_ISVTX) bit is set.
x The file is executable or the directory is searchable.
- None of the above apply.
The last character is a plus sign ``+'' if any there are any alternate or additional access control methods associated with the inode, other-
wise it will be a space.
SEE ALSO
chmod(1), find(1), stat(2), getmode(3), setmode(3)
HISTORY
The strmode() function first appeared in 4.4BSD.
BSD July 28, 1994 BSD
