Sponsored Content
Operating Systems Solaris Help mounting nfs on boot on Solaris 11 Post 302601034 by rdhalstead on Wednesday 22nd of February 2012 06:02:53 PM
Old 02-22-2012
Consider using the automounter.
This User Gave Thanks to rdhalstead For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

solaris 8 NFS mounting problem

While mounting nfs file system I get the following error . # mount -F nfs jewelex:/back2 /oback2 nfs mount: jewelex:/back2: Permission denied Following is the permission for oback2 drwxr-xr-x 2 root other 512 Apr 9 18:39 oback2 Directory permission on jewelex server is ... (4 Replies)
Discussion started by: Hitesh Shah
4 Replies

2. Linux

NFS not mounting during kickstart

Hi, Re-building linux server from a kickstart image on cdrom. We have a kickstart server. the cdrom contacins the kickstart ks.cfg file and does a NFS mount from an IP to load the iso images and other files needed during the kickstart (re-build) Now for some reason the kickstart stops and... (2 Replies)
Discussion started by: Andrek
2 Replies

3. Solaris

problem NFS mounting onto Solaris 10

On my Solaris 10 server, I want to share out the directory /export/home/data, so in the /etc/dfs/dfstab file, I have this line: share -F nfs -o rw /export/home/data In the /etc/hosts.equiv file, I have this: + When I do a "ps -ef" command, I see that the "nfsd' daemon is started. ... (2 Replies)
Discussion started by: serendipity1276
2 Replies

4. Solaris

Mounting a NFS network file system across platforms - Solaris to AIX

Hi all, Kind of an emergency situation, I have to NFS mount an AIX filesystem on to a Sun Solaris OS (5.10). Typically from Sun to Sun is: mount -F nfs <remote file system>/dir <mount point> Which of course doesn't work if the remote file system is another OS (like AIX). Is there... (1 Reply)
Discussion started by: jeffpas
1 Replies

5. UNIX for Dummies Questions & Answers

Mounting NFS filesystem

Hi All, I need to mount an nfs filesystem as below. xxx.xx.xx.xxx:/media/nss/Rocky Catherine/logs For the above as there is space in between the name, hoping it will not mount, if i give it with double quotes as below will it work? mount "xxx.xx.xx.xxx:/media/nss/Rocky... (2 Replies)
Discussion started by: Rockyc3400
2 Replies

6. Red Hat

NFS not mounting using ipaddress of client

Dear All, I have an NFS Server and client. I am trying to include the ipaddress of the client in servers exports file /etc/exports. In this case , I could not mount , saying permission denied. But when I give * symbol in the place of ipaddress ( Global , any IPS ) it is mounting. ... (1 Reply)
Discussion started by: jegaraman
1 Replies

7. Red Hat

NFS mounting from client pc

The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports i have added the following line /home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash) i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (1 Reply)
Discussion started by: ainstin
1 Replies

8. Red Hat

NFS mounting issue

The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports i have added the following line /home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash) i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (5 Replies)
Discussion started by: ainstin
5 Replies

9. Solaris

Mounting 2012R2 NFS Share on Solaris 10

Hi all, new here. I'm attempting to mount an NFS share I've created on a 2012r2 esx VM on my solaris 10 vm, I'm using the following command: mount 2012box:/sharename /mnt and I get the following result: nfs mount: mount: /mnt: Operation not supported Both vms can ping one... (3 Replies)
Discussion started by: Meshuggener
3 Replies

10. Solaris

Mounting NFS

Hi, I am having some issues mounting NFS files. for some reason the mount -F nfs is not being recognized.. bash-3.2# mount -F nfs -o rw 192.168.245.129:/mnt/nfs1/ /mnt UX:vxfs mount: ERROR: V-3-20135: FSType nfs not recognized UX:vxfs mount: INFO: V-3-20147: Usage: mount {special |... (5 Replies)
Discussion started by: br1an
5 Replies
AMQ(8)							      System Manager's Manual							    AMQ(8)

NAME
amq - automounter query tool SYNOPSIS
amq [ -fmpqsvwHTU ] [ -h hostname ] [ -l log_file ] [ -x log_options ] [ -D debug_options ] [ -P program_number ] [[ -u ] directory ... ] DESCRIPTION
Amq provides a simple way of determining the current state of amd program. Communication is by RPC. Three modes of operation are sup- ported by the current protocol. By default a list of mount points and auto-mounted filesystems is output. An alternative host can be specified using the -h option. If directory names are given, as output by default, then per-filesystem information is displayed. OPTIONS
-f Ask the automounter to flush the internal caches and reload all the maps. -h hostname Specify an alternate host to query. By default the local host is used. In an HP-UX cluster, the root server is queried by default, since that is the system on which the automounter is normally run. -l log_file Tell amd to use log_file as the log file name. For security reasons, this must be the same log file which amd used when started. This option is therefore only useful to refresh amd's open file handle on the log file, so that it can be rotated and compressed via daily cron jobs. -m Ask the automounter to provide a list of mounted filesystems, including the number of references to each filesystem and any error which occurred while mounting. -p Return the process ID of the remote or locally running amd. Useful when you need to send a signal to the local amd process, and would rather not have to search through the process table. This option is used in the ctl-amd script. -q Suppress error messages produced when attempting synchronous unmounts with the -u option. -s Ask the automounter to provide system-wide mount statistics. -u Ask the automounter to unmount the filesystems named in directory instead of providing information about them. Unmounts are requested, not forced. They merely cause the mounted filesystem to timeout, which will be picked up by amd's main scheduler thus causing the normal timeout action to be taken. If the -u option is repeated, amq will attempt to unmount the file system syn- chronously by waiting until the timeout action is taken and returning an error if the unmount fails. Any error messages produced may be suppressed with the -q option. -v Ask the automounter for its version information. This is a subset of the information output by amd's -v option. -w Translate a full pathname as returned by getcwd(3) into a short Amd pathname that goes through its mount points. This option requires that Amd is running. -x log_options Ask the automounter to use the logging options specified in log_options from now on. Note that the "fatal" and "error" options can- not be turned off. -D debug_options Ask the automounter to use the debugging options specified in debug_options from now on. -H Display short usage message. -P program_number Contact an alternate running amd that had registered itself on a different RPC program_number and apply all other operations to that instance of the automounter. This is useful when you run multiple copies of amd, and need to manage each one separately. If not specified, amq will use the default program number for amd, 300019. For security reasons, the only alternate program numbers amd can use range from 300019 to 300029, inclusive. -T Contact amd using the TCP transport only. Normally amq will try TCP, and if that failed, will try UDP. -U Contact amd using UDP (connectionless) transport only. Normally amq will try TCP, and if that failed, will try UDP. FILES
amq.x RPC protocol description. CAVEATS
Amq uses a Sun registered RPC program number (300019 decimal) which may not be in the /etc/rpc database. If the TCP wrappers library is available, and the use_tcpwrappers global amd.conf option is set to ``yes'', then amd will verify that the host running amq is authorized to connect. The amd service name must used in the /etc/hosts.allow and /etc/hosts.deny files. For example, to allow only localhost to connect to amd, add this line to /etc/hosts.allow: amd: localhost and this line to /etc/hosts.deny: amd: ALL SEE ALSO
amd(8), amd.conf(5), hosts_access(5). ``am-utils'' info(1) entry. Linux NFS and Automounter Administration by Erez Zadok, ISBN 0-7821-2739-8, (Sybex, 2001). http://www.am-utils.org Amd - The 4.4 BSD Automounter AUTHORS
Jan-Simon Pendry <jsp@doc.ic.ac.uk>, Department of Computing, Imperial College, London, UK. Erez Zadok <ezk@cs.sunysb.edu>, Computer Science Department, Stony Brook University, Stony Brook, New York, USA. Other authors and contributors to am-utils are listed in the AUTHORS file distributed with am-utils. 25 April 1989 AMQ(8)
All times are GMT -4. The time now is 04:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy