9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm trying to do this exact same thing, so far I have created this to move files
i've named my script CP.sh
#!/bin/bash
cd /root/my-documents/NewDir/
for f in *.doc
do cp -v $f root/my-documents/NewDir $f{%.doc}
done
When i go to run this in the console i type, bin/sh/ CP.sh
but it... (7 Replies)
Discussion started by: MKTM_93_SIMP
7 Replies
2. Shell Programming and Scripting
All,
I need to grab and rename common files from several unique directory structures. For example, the directory structures looks like:
/unique_dir/common/common/common/person_name_dir/common_file.txt
There are over 90,000 of these text files that I'd like to put in a single directory as... (5 Replies)
Discussion started by: hburnswell
5 Replies
3. Shell Programming and Scripting
Hi All,
I am doing this for svn patch making. I got the list of files to make the patch. I have the list in a file with path of all the files.
To Do
From Directory : /myproject/MainDir
To Directory : /myproject/data
List of files need to copy is in the file: /myproject/filesList.txt
... (4 Replies)
Discussion started by: linuxadmin
4 Replies
4. Shell Programming and Scripting
Hi All,
I'm trying to list some files from my log directory
and files are like this
log.20110302_20.gz
log.20110302_21.gz
log.20110302_22.gz
log.20110302_23.gz
log.20110303_00.gz
log.20110303_01.gz
log.20110303_02.gz
............
log.20110311_22.gz
log.20110311_23.gz... (2 Replies)
Discussion started by: thelakbe
2 Replies
5. UNIX for Advanced & Expert Users
I am userB and have a dir
/temp1
This dir is owned by me.
How do I recursively copy files from another users's dir userA?
I need to preserve the original user who created files, original group information, original create date, mod date etc.
I tried
cp -pr /home/userA/* .
... (2 Replies)
Discussion started by: Hangman2
2 Replies
6. Solaris
Hi,
I understand that to copy files across server, the feasible way will be using scp command. Am I right?
What if the two servers are not connected to a network? If by using a cross cable to link up both the server, what will be the best (fastest) way to copy files across? scp as well?
... (3 Replies)
Discussion started by: user50210
3 Replies
7. Shell Programming and Scripting
hi
I want to copy all files from the current directory and move to .archive file.
Moreover,I want to add .bak to each file name, that will be copied.
How can I do that? (4 Replies)
Discussion started by: tjay83
4 Replies
8. Solaris
I am new user to solaris and installed solaris operating system on full Harddisk 120Gb. I am unable to copy music files to desktop and /home directory.
One thing happened while registering is- i entered login-root and its password. The message prompted your system is crashed. Is it because of... (1 Reply)
Discussion started by: patilmukundraj
1 Replies
9. UNIX for Dummies Questions & Answers
I like to know the command structure of copying files/directories from a unix box using telnet session to a windows box. (4 Replies)
Discussion started by: alpheusm
4 Replies
nfslog.conf(4) File Formats nfslog.conf(4)
NAME
nfslog.conf - NFS server logging configuration file
SYNOPSIS
/etc/nfs/nfslog.conf
DESCRIPTION
The nfslog.conf file specifies the location of the NFS server logs, as well as the location of the private work files used by the NFS
server and nfslogd(1M) daemon during logging. Each entry in the file consists of a mandatory tag identifier and one or more parameter iden-
tifiers. The parameter identifier specifies the value or location of the specific parameter. For instance, the parameter identifier
"log=/var/nfs/logs/serverLog" specifies the location of the NFS server activity log. The mandatory tag identifier serves as an index into
the /etc/nfs/nfslog.conf file to identify the various parameters to be used. At export time, the share_nfs(1M) command specifies the NFS
server logging parameters to use by associating a tag from the /etc/nfs/nfslog.conf file to the exported file system. It is legal for more
than one file system to be exported using the same logging tag identifier.
NFS server logging is not supported on Solaris machines that are using NFS Version 4.
A "global" tag identifier is included in /etc/nfs/nfslog.conf. It specifies the default set of values to be used during logging. If no tag
identifier is specified at export time, then the values in the "global" entry are used. The "global" values can be modified by updating
this entry in /etc/nfs/nfslog.conf.
Each entry in the file must contain a mandatory tag identifier and at least one parameter/value pair. If a parameter is not specified in a
given entry, the global value of the parameter will be used. The exact entry syntax follows:
<tag> [defaultdir=<path>] [log=<path><file>]
[fhtable=<path><file>] [buffer=<path><file>] [logformat=basic|extended]
defaultdir=<path>
Specifies the directory where the logging files and working files will be placed. This path is prepended to all relative paths speci-
fied in other parameters.
log=<path><file>
Specifies the location of the user-readable log file. The log will be located in the defaultdir, unless <path> is an absolute path.
fhtable=<path><file>
Specifies the location of the private file handle to path mapping database files. These database files are for the private use of the
NFS server kernel module and the nfslogd daemon. These files will be located in the defaultdir, unless <path> is an absolute path.
These database files are permanently stored in the file system. Consult nfslogd(1M) for information on pruning the database files.
buffer=<path><file>
Specifies the location of the private work buffer file used by the NFS server kernel module to record raw RPC information. This file
is later processed by the nfslog daemon, which in turn generates the user-readable log file. This work buffer file will be located in
the defaultdir, unless <path> is an absolute path.
logformat=basic|extended
Sets the format of the user-readable log file. If not specified, the basic format is used. The basic format is compatible with log
files generated by the Washington University FTPd. The extended format provides a more detailed log, which includes directory modifica-
tion operations not included in the basic format, such as mkdir, rmdir and remove. Note that the extended format is not compatible with
Washington University's FTPd log format.
EXAMPLES
Example 1: Using the global Tag
The "global" tag may be modified so that all exported file systems that enabled logging use a common set of parameters that conform to the
specific needs of the user. These values are used until a specific tag identifier overrides them.
global defaultdir=/var/nfs log=logs/nfslog
fhtable=tables/fhtable buffer=buffers/nfslog_workbuffer
logformat=basic
Example 2: Overriding the Global defaultdir and logformat
Because log files can become very large, it may be desirable to store the logs and working files in separate file systems. This can be eas-
ily accomplished by simply specifying a different defaultdir for every file system exported by means of a unique tag:
engineering defaultdir=/engineering/logging
logformat=extended
accounting defaultdir=/accounting/logging
marketing defaultdir=/marketing/logging
File systems shared with the engineering identifier will have their logs and workfiles located in /engineering/logging. For instance, the
log file will be located at /engineering/logging/logs/nfslog. Note that the engineering log file will be stored in the extended format,
while the rest of the log files will remain in the basic format.
Any of the parameters can be updated in a tag identifier, which overrides the global settings.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnfssr |
+-----------------------------+-----------------------------+
SEE ALSO
nfslogd(1M), share_nfs(1M), attributes(5)
NOTES
Logs, work files, and file handle to path mapping database can become very large. Be aware of appropriate placement within the file system
name space. See nfslogd(1M)) for information on pruning the database files and cycling logs.
SunOS 5.10 2 Dec 2004 nfslog.conf(4)