I've experienced this problem in the past and remember having to fight it.
I recommend that you ease all security until you make is work and then tighten up afterwards. I can confirm that it can be made to work with RHEL.
1.
Start by opening up root access to the Solaris share:
Put the RHEL nodename and its ip address in /etc/hosts
2.
Set the access rights on the Solaris share to 777.
For good measure also set 777 on its parent directory
3.
On RHEL try:-
mount <Solaris ip>:/var/share <mount point>
You may also need to try specifying nfs version 2,3 or 4 on the mount command. Try all three versions to test.
Post the results of that.
I think you'll agree that it's easier to troubleshoot from a working position than a non-working position. You can then re-tighten security until you break it.
Hi,
my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client.
I always got the messages no permission.
Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Hi all,
Hopefully this question hasn't been asked a thousand times. I am trying to connect a Windows Server to an exported NFS share which resides on an AIX box.
I think the directory is exported correctly from the AIX side but I can't verify that because I didn't do it myself. On the... (6 Replies)
Hi,
I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error:
# mount 128.127.11.121:/aix /to_be_del
mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper
failure - RPC: 1832-008 Timed out
mount: retrying... (1 Reply)
I ve a client : <clientname> and a server: <servername>
Both of them running: HPUX B.11.31
SERVER outputs:
I ve shared a folder in <servername> called /test and the O/P for
# exportfs
- /test root=<clientname>,rw=<clientname>,ro ""
# showmount -e
export list for... (6 Replies)
When i tried to mount the nfs i see this error message
mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount
mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied
and the /etc/exports file in the host side looks like this
/remote/proj1 ... (12 Replies)
Hi,
I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server.
On the NFS Server, in /etc/dfs/, I added following line to dfstab file.
& then ran the following
On the client machine, while running the mount command, I am... (0 Replies)
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)
I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
My customer has created a share on a Windows Server 2012 system and exported it as a NFS share.
I can mount the share on a SCO system, but I only have read/write access. So I am unable to list the contents of the share. It is as if the directories had 0666 permissions.
My customer says that this... (5 Replies)
Discussion started by: jgt
5 Replies
LEARN ABOUT DEBIAN
pmvarrun
pmvarrun(8) pam_mount pmvarrun(8)Name
pmvarrun - updates /var/run/pam_mount/user
Syntax
pmvarrun -u user [options]
Description
A separate program is needed so that /var/run/pam_mount/user may be created with a pam_mount-specific security context (otherwise SELinux
policy will conflict with gdm, which also creates file in /var/run).
pmvarrun is flexible and can run in a number of different security setups:
root-root
When pmvarrun is invoked as root, /var/run/pam_mount's permission settings can be as strict as needed; usually (0755,root,root) is a good
pick as it gives users the debug control over their refcount. Refcount files are given their respective owners (chowned to the user who
logs in).
user-user
When invoked as the user who logs in, /var/run/pam_mount needs appropriate permissions to create a file, which means the write bit must be
set. It is also highly suggested to set the sticky bit in this case, so other users do not tamper with your refcount.
root-user
Some programs or login helpers incorrectly call the PAM stack in a way that the login phase is done as root and the logout phase as a nor-
mal user. Nevertheless, pmvarrun supports this, and the same permissions as in root-root can be used. While the user may not be able to
unlink his file from /var/run/pam_mount, it will be truncated to indicate the same state.
Options--help, -h
Display help.
--user user, -u user
User to handle, must be a valid username.
--operation number, -o number
Increase volume count by number.
-d Turn on debugging.
Files
/var/run/pam_mount/user
Author
This manpage was originally written by Bastian Kleineidam <calvin@debian.org> for the Debian distribution of libpam-mount but may be used
by others.
See /usr/share/doc/packages/libpam-mount/copyright for the list of original authors of pam_mount.
pam_mount 2008-10-08 pmvarrun(8)