Thank you for the reply. Actually, I believe I described the desired command output poorly. In the snippet I posted, the 'exports' array would define the resources that I'd want to define:
So the commands I'd want to run would be:
Notice the need to increment the 'fsid' based upon the exported directory (media=1, hotdrive=2, images=3). If a given directory is exported to multiple subnets, it will maintain the same 'fsid'.
hello,
During the cluster installation, we are required to enter a cluster name. When this name is used?
I have a shared disk between those 2 nodes. To test NFS failover, what should I do?
PS: I am using VCS 5
thanks (5 Replies)
Hello
I have a directory structure with year in format 4 digits, e.g 2009, below which is month format 1 or 2 digits, e.g 1 or 12, blow which is day format 1 or 2 digits, e.g 1 or 31.
I want to change the names of lots of directories to the be
Year - 4 digits , e.g 2009 - No change here... (4 Replies)
Hello, I am new to the whole "scripting" thing. Below is the script that I have so far and where i need the Variables to go (VAR#)
#!/bin/bash
#Sample Script
VAR1=
echo "Choose an option: 1) Create a file. 2) Delete a file. 3) Move a file."
read VAR1
case $VAR1 in
1)
echo "Pick... (4 Replies)
Hi, I have a bunch of media files in a directory that have been converted (from MTS to MOV format), so my directory contains something like this:
clip1.mts
clip1.mov
clip2.mts
clip2.mov
The problem is that the .mov files that have been created have the timestamps of the conversion task,... (2 Replies)
Hi All,
Need your help to resolve below error in cluter.
Sep 9 05:37:30 node2 rgmanager: Starting disabled service service:Prod_Service
Sep 9 05:37:30 node2 rgmanager: HA LVM: Improper setup detected
Sep 9 05:37:30 node2 rgmanager: * initrd image needs to be newer than lvm.conf... (3 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)
Hi Everybody,
I'm a newbie to shell scripting, and I'd appreciate some help. I have a bunch of .txt files that have some unwanted content. I want to remove lines 1-3 and 1028-1098.
#!/bin/bash
for '*.txt' in <path to folder>
do
sed '1,3 d' "$f";
sed '1028,1098 d' "$f";
done
I... (2 Replies)
I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online.
I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies
LEARN ABOUT ULTRIX
exports
exports(5nfs)exports(5nfs)Name
exports - defines NFS file systems to be exported
Syntax
/etc/exports
Description
The file describes the local file systems and directories that can be mounted by remote hosts through the use of the NFS protocol. The
file can also be used to restrict access to a particular set of remote systems. The request daemon accesses the file each time it receives
a mount request from an NFS client.
Each entry in the file consists of a file system or directory name followed by an optional list of options or an optional list of identi-
fiers or both. The identifiers define which remote hosts can mount that particular file system or directory. The identifiers listed beside
the name of each file system or directory can be either host names or YP netgroups names. When the daemon receives a mount request from a
client, it searches for a match in the list of identifiers, first by checking the client host name with the host name identifiers and sec-
ond by checking the client host name in a YP netgroups. When it finds a match, makes that file system or directory available to the
requesting client.
The exports file format is defined as follows:
pathname [-r=#] [-o] [identifier_1 identifier_2 ... identifier_n]
or
#anything
Name of a mounted local file system or a directory of a
mounted local file system . The must begin in column 1.
options:
-r=# Map client superuser access to uid #. If you want to allow client superusers access to the file system or directory
with the same permissions as a local superuser, use Use only if you trust the superuser on the client system. The
default is which maps a client superuser to nobody. This limits access to world readable files.
-o Export file system or directory read-only.
The options can be applied to both file system and directory entries in
identifiers: Host names or netgroups, or both, separated by white space, that specify the access list for this export. Host names can
optionally contain the local BIND domain name. For more information on BIND, see the Guide to the BIND/Hesiod Service If no
hosts or netgroups are specified, the daemon exports this file system or directory to anyone requesting it.
A number sign (#) anywhere in the line marks a comment that extends to the end of that line.
A whitespace character in the left-most position of a line indicates a continuation line.
Each file system that you want to allow clients to mount must be explicitly defined. Exporting only the root (/) will not allow clients to
mount Exporting only will not allow clients to mount if it is a file system.
Duplicate directory entries are not allowed. The first entry is valid and following duplicates are ignored.
Desired export options must be explicitly specified for each exported resource: file system or directory. If a file system and subdirecto-
ries within it are exported, the options associated with the file system are not ``inherited''. You do not need to export an entire file
system to allow clients to mount subdirectories within it.
The access list associated with each exported resource identifies which clients can mount that resource with the specified options. For
example, you can export an entire file system read-only, with a subdirectory within it exported read-write to a subset of clients. If a
client that is not identified in the export access list of a directory attempts to mount it, then access is checked against the closest
exported ancestor. If mount access is allowed at a higher level in the directory tree of the file system, the export options associated
with the successful match will be in effect.
If you are concerned with nfs security, all ufs file systems exported via nfs should be ufs mounted with the option. All ufs file systems
exported via nfs with the option specified in the file should be ufs mounted with the option.
Examples
/usr alpha beta # export /usr to hosts alpha and beta, client
superuser maps to uid -2 and read-write
access is permitted
/usr/staff/doe clients # export directory to hosts in netgroup clients
/usr/man/man1 -o # export directory read-only to everyone
/usr/local -r=0 beta # export file system to beta, superuser
on beta maps to local superuser (uid=0)
FilesSee Alsohosts(5), mountd(8nfs), netgroup(5yp)
Guide to the BIND/Hesiod Service
Introduction to Networking and Distributed System Services
exports(5nfs)