10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Can any one give a explaination with examples on how to understand file transmission log files in Unix for inbound and outbound traffic. (1 Reply)
Discussion started by: ITDev01
1 Replies
2. Shell Programming and Scripting
I am executing a stored procedure through shell script. In the procedure, i have dbms_output.put_line to log the comments. This is working fine and but logs are available only after the execution of the pl/sql procedure's completion.
I want to print the log comments while executing the procedure... (2 Replies)
Discussion started by: vel4ever
2 Replies
3. HP-UX
Hi,
Hope its good with everyone.
I have the below su logs and i dont understand the bolded numbers. can someone help me please.
Jul 24 11:55:50 su: - 8 username
Jul 24 12:12:40 su: - 10 username
Jul 26 11:15:32 su: - 7 username
I understand these are failed logins but what does that... (1 Reply)
Discussion started by: indraseng
1 Replies
4. UNIX for Advanced & Expert Users
Hi.
Is there a way or command (other than netstat) in Unix to find out or get a list a users who FTP into a particular server? Like, say last 1000 users. I need to get the user ID (any info), who FTP to a particular server.
netstat gives only the users who have an FTp session currently.
... (4 Replies)
Discussion started by: manisendhil
4 Replies
5. UNIX for Advanced & Expert Users
Hi !
I have a FTP site, where I softlinked my server log file.
Now I want to view the logs in IE as I do in unix
Some kind of free tool should be there, Can somebody provide me a pointer.
Thanks. (0 Replies)
Discussion started by: dashok.83
0 Replies
6. Linux
Hi,
I need to get a hostory of users who FTP into a server. How can I do it in Linux/Unix? Is there a command for this? I do not want to use netstat -a as it gives only the list of users who have a session currently on the server. Can this be done with the "last" command?
Please do let me... (0 Replies)
Discussion started by: manisendhil
0 Replies
7. UNIX for Dummies Questions & Answers
Hi.
Is there a way or command (other than netstat) in Unix to find out or get a list a users who FTP into a particular server? Like, say last 1000 users. I need to get the user ID (any info), who FTP to a particular server.
netstat gives only the users who have an FTp session currently.
... (2 Replies)
Discussion started by: manisendhil
2 Replies
8. IP Networking
hi
i am having problem with proxy logs
the log file in /var/log/squid/access.log is having 0 size
i am using red hat linux enterprise edition
squid version->Version 2.5.STABLE6 with default conf file
and it is running but whatever i access from internet it is not... (1 Reply)
Discussion started by: madhusudankh
1 Replies
9. HP-UX
Hi All,
Can anybody tell me, how to trace out user access to the Unix Server Machine, (i,e) I want to find out the user who had executed some commands to alter the cron file.
Regards
Nag (3 Replies)
Discussion started by: nag_sundaram
3 Replies
10. UNIX Desktop Questions & Answers
hi
my name es juan
i have sco open server 5.0.4 release
i need clear the log files as wtmp
thanks you very much (1 Reply)
Discussion started by: jtapia
1 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 specified 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 modification 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.11 2 Dec 2004 nfslog.conf(4)