10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I've come accross a situation where I need to exit from current shell script at the same time I need to start/activate another shell script.
How can I do that in KSH ?? Need help !!
For example, my script is as below
#!/bin/ksh
paramFile="/home/someXfile.lst"
] && <<Here I... (1 Reply)
Discussion started by: R0H0N
1 Replies
2. Shell Programming and Scripting
Good morning dear friends,
I want to write an UNIX script to do the following task:
We have 6 directories, called (SMS_01, SMS_02 ....... SMS_06), some files are distributed across these directories, but the distribution process is not good, I mean when I check these directories I found the... (14 Replies)
Discussion started by: Mohannad
14 Replies
3. Shell Programming and Scripting
first of all I thought the argument DONE is necessary for all scripts that have or begin with do statements which I have on my script, However, I still don't completely understand why I am receiving an error I tried adding another done argument statement but didn't do any good.
I appreciate... (3 Replies)
Discussion started by: wolf@=NK
3 Replies
4. Shell Programming and Scripting
All
i am new to linux, and try to have a simple expect script to ssh then telnet to the network equipment, and exit itself. but dont know why i hang at the last $
#!/usr/bin/expect
set timeout 10
set arg
set arg1
spawn ssh -l UserA 1.1.1.1
expect "assword:";
send "PasSwOrD\r";... (1 Reply)
Discussion started by: samoptimus
1 Replies
5. Shell Programming and Scripting
Hi All,
Can anyone help me to finish the scripts. this scripts is
this scripts will run on crontab in every 4 minutes to get the newest router interface status.
I would like to add a function to count the router interface flapping, if more than 2 times in 20 minutes (scripts run 5 times)... (1 Reply)
Discussion started by: momo0617
1 Replies
6. Shell Programming and Scripting
Hello,
I'm doing a script where I'm traveling a file, and moves down line by line, and is copied to another file, up to the line 100, then the smaller file passes to another format ... but the problem I have is that if there are 357 lines for example, file 1 2 i 3, converted correctly but the 4... (1 Reply)
Discussion started by: uri_crack
1 Replies
7. UNIX for Dummies Questions & Answers
Hi there,
I wanted to write a finish script for my jumpstart server which creates a ntp.conf file and enables ntp on the client machines during installation. Is that possible?
Thanks for the help :)
P.S. I'm a real Solaris noob, so do excuse me if I sound like an idiot..lol (1 Reply)
Discussion started by: iman453
1 Replies
8. UNIX for Advanced & Expert Users
Hi,
I have strange problem executing some command on solaris 5.9
ps command does not finish(hangs) and runs forever without any result.
same with cc command too.Please suggest (1 Reply)
Discussion started by: Raom
1 Replies
9. UNIX for Dummies Questions & Answers
i tried to build a command to replaces the word "include" with
"exclude"
in each *.h type of file in a certain directory
and to display the lines in which the switch happened.
i did a command and i dont know why its not working
find /usr -name "*.h" -exec sed 's/include/exclude/g' {} \;... (2 Replies)
Discussion started by: newby2
2 Replies
10. Shell Programming and Scripting
Hi,
I want to know is there a way out wherein we can know that the C++ executable has finished its task.
Following is the steps:
1.Shell script calls a executable after setting all the env variables.
2.Now after the executable has done its job(basically to create some outpur files).The... (2 Replies)
Discussion started by: electroon
2 Replies
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)
Files
See Also
hosts(5), mountd(8nfs), netgroup(5yp)
Guide to the BIND/Hesiod Service
Introduction to Networking and Distributed System Services
exports(5nfs)