10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
i am new to scripting ,i need bash script in jump server to pull the /etc/passwd of all servers and the ssh keys are installed (3 Replies)
Discussion started by: profiles
3 Replies
2. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
3. Solaris
Hello,
I am new to Solaris. However, I was able to configure the Syslog server on Solaris. I am using a windows client to send logs to my Solaris syslog server. this is working fine. however, I have 23 servers which are sending their logs to the syslog server and it is very difficult to read all... (2 Replies)
Discussion started by: ravmohun
2 Replies
4. Red Hat
We have RHEL 5.8 in our environment, I had a query whether we can implement an FTP server using vsftpd package and Linux configurations like setsebool without using any external FTP clients like FileZilla etc. I am very confused on this. The FTP functionalities that should be present are download &... (3 Replies)
Discussion started by: RHCE
3 Replies
5. UNIX for Advanced & Expert Users
Hello All,
I am working on SuSe Linux Platform. Some times ago i got an issue with an application for which i had to update that in all desktops (SLED == SuSe Linux Desktop).
Since this time number of desktops were less then it was possible to go and update package manually. But in... (1 Reply)
Discussion started by: shirsha
1 Replies
6. Shell Programming and Scripting
Hello everybody,
I have one small issue... :(
When i'm trying to connect another unix box through below script..
#!/usr/bin/bash
ssh $1 <<EOF
Commands
.
.
exit
EOF
But getting some syntax error "-sh: syntax error at line 2: `end of file' unexpected". I used to use... (2 Replies)
Discussion started by: raghu.iv85
2 Replies
7. Linux
Hi, I bought a linux server, and actually all I can do now is enter through the SSH, This is my first time buying a server. When I bought a VPS before I could enter through remote desktop control, how can I do that on the server ? I need a little explanation because I am little short on info here... (1 Reply)
Discussion started by: Thehunterman
1 Replies
8. UNIX for Dummies Questions & Answers
hi,
i am beginner i am using small lan setup all machine fc 6 and fc7 8 and fedora 9 also i want to know how to configure centralized log server on fedora 9 step by step any one help me
Thanks (0 Replies)
Discussion started by: poswer
0 Replies
9. UNIX for Advanced & Expert Users
I have a syslog server running Solaris 5.9 that is used exclusively to receive log messages from several thousand Cisco devices. The syslog server is and has been running fine for several months..
I would like to take all messages logged from the Cisco devices on this server and forward them... (2 Replies)
Discussion started by: getwithrob
2 Replies
10. Shell Programming and Scripting
Hi,
I want to log-in to a remote server using shell script.
The server requires the following while allowing a connection:
username
password
one - letter authorisation.
How can i implement this in my script?
thanks,
abey (6 Replies)
Discussion started by: abey
6 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)