08-30-2008
Zaxxon has already pointed out the problem in the other thread:
Quote:
0042-124 c_ch_nfsexp : option NFS sec=sys isn't supported
Thread opener perhaps tries to create an mksysb resource using NIM from the NIM master but already has NFS-exported (probably manually) parts or the whole exports directory. As NIM creates a new entry in /etc/exports and reexports all the NFS shares (again) this leads to all kinds of problems.
Solution: remove you manually created NFS share from /etc/exports during NIM operations. This is a known issue with NIM.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi,
i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work on and off for about a... (1 Reply)
Discussion started by: boredazfcuk
1 Replies
2. UNIX for Dummies Questions & Answers
hi,
i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work for about a month with no... (2 Replies)
Discussion started by: boredazfcuk
2 Replies
3. UNIX for Dummies Questions & Answers
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in... (4 Replies)
Discussion started by: astjen
4 Replies
4. AIX
Hi,
I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master")
The backup starts, but doesn't success.
Thanks if you can help me to resolve this problem :
Creating information file (/image.data) for rootvg...
Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies
5. Shell Programming and Scripting
Usually we use !/usr/bin/ksh at the start of the script.But if I am having this stuff in the scripts and calling one script from other its not working.What may be the reason behind it ?
xyz.ksh
#!/usr/bin/ksh
echo "Hi"
abc.ksh
#!/usr/bin/ksh
echo "I am fine"
ksh xyz.ksh
Its... (4 Replies)
Discussion started by: dr46014
4 Replies
6. AIX
Hello,
I use commands savevg & mksysb to do backups on an AIX server.
Frequently, I have a return code 3.
I would know why, but after searches, I did'nt find.
If somebody know ... Tell me.
Thanks.
emetra (2 Replies)
Discussion started by: emetra
2 Replies
7. Red Hat
Hi All,
I have RHEL 5 installed in my system. Something must has happened because when i reboot the server, it came with many error..
/usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0. Can't open shared object files. No such file/directory
It finnaly ends with the... (6 Replies)
Discussion started by: IgnitedMind
6 Replies
8. UNIX and Linux Applications
I am installing lxml module for python on redhat
I have installed libxml2 already.
When I run for libxslt:
./configure --prefix=libxslt_folder --with-libxml-prefix=libxml2_folder
It is ok
the I run :
make
I have error:
/usr/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
I... (4 Replies)
Discussion started by: AIX_30
4 Replies
9. Shell Programming and Scripting
I have this scp script running,
/usr/bin/scp -r /cerner/mgr --exclude-from=/atg/move_exclude.dat 102.126.112.68:/cerner
but am getting an error:
--exclude-from=/atg/move_exclude.dat: No such file or directory
I am wondering if the syntax is incorrect...
I also have additional... (3 Replies)
Discussion started by: Daniel Gate
3 Replies
10. Shell Programming and Scripting
Hi,
I installed ruby using rvm with root user on Linux.
Now i m trying the below command as a non root user with sudo privileges.
sudo /usr/local/rvm/rubies/ruby-2.2.5/bin/gem install passenger
I get the below error:
I had even reset the path for both gem as well as ruby as you... (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT REDHAT
rpc.mountd
rpc.mountd(8) System Manager's Manual rpc.mountd(8)
NAME
rpc.mountd - NFS mount daemon
SYNOPSIS
/usr/sbin/rpc.mountd [options]
DESCRIPTION
The rpc.mountd program implements the NFS mount protocol. When receiving a MOUNT request from an NFS client, it checks the request against
the list of currently exported file systems. If the client is permitted to mount the file system, rpc.mountd obtains a file handle for
requested directory and returns it to the client.
Exporting NFS File Systems
Making file systems available to NFS clients is called exporting.
Usually, a file system and the hosts it should be made available to are listed in the /etc/exports file, and invoking exportfs -a whenever
the system is booted. The exportfs(8) command makes export information available to both the kernel NFS server module and the rpc.mountd
daemon.
Alternatively, you can export individual directories temporarily using exportfs's host:/directory syntax.
The rmtab File
For every mount request received from an NFS client, rpc.mountd adds an entry to the /var/lib/nfs/rmtab file. When receiving an unmount
request, that entry is removed. user level part of the NFS service.
However, this file is mostly ornamental. One, the client can continue to use the file handle even after calling rpc.mountd 's UMOUNT proce-
dure. And two, if a client reboots without notifying rpc.mountd , a stale entry will remain in rmtab.
OPTIONS
-d kind or --debug kind
Turn on debugging for kind.
-F or --foreground
Run in foreground (do not daemonize)
-f or --exports-file
This option specifies the exports file, listing the clients that this server is prepared to serve and parameters to apply to each
such mount (see exports(5)). By default, export information is read from /etc/exports.
-h or --help
Display usage message.
-o num or --descriptors num
Set the limit of the number of open file descriptors to num. The default is 256.
-N or --no-nfs-version
This option can be used to request that rpc.mountd do not offer certain versions of NFS. The current version of rpc.mountd can sup-
port both NFS version 2 and the newer version 3. If the NFS kernel module was compiled without support for NFSv3, rpc.mountd must be
invoked with the option --no-nfs-version 3 .
-n or --no-tcp
Don't advertise TCP for mount.
-P Ignored (compatibility with unfsd??).
-p or --port num
Force rpc.mountd to bind to the specified port num, instead of using the random port number assigned by the portmapper.
-V or --nfs-version
This option can be used to request that rpc.mountd offer certain versions of NFS. The current version of rpc.mountd can support both
NFS version 2 and the newer version 3.
-v or --version
Print the version of rpc.mountd and exit.
TCP_WRAPPERS SUPPORT
This rpc.mountd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.mountd if they should be
allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:
mountd: .bar.com
You have to use the daemon name mountd for the daemon name (even if the binary has a different name).
For further information please have a look at the tcpd(8) and hosts_access(5) manual pages.
SEE ALSO
rpc.nfsd(8), exportfs(8), exports(5), rpc.rquotad(8).
FILES
/etc/exports, /var/lib/nfs/xtab.
AUTHOR
Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others.
25 Aug 2000 rpc.mountd(8)