Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
UNICEF

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 184 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

evlog



DESCRIPTION

       Event  logging  implements  the  proposed POSIX Standard -
       Event Logging [C Language]. In this implementation,  event
       records  are  stored in binary format. Binary records give
       you the ability to capture sophisticated event records but
       they  require  you  to use specialized commands to create,
       view and maintain event logs and event records. This  man­
       page  describes  the  set of specialized commands and ser­
       vices that support event logging.

       By default, event logging creates two logs:

       /var/evlog/eventlog
              Eventlog is the primary system log. It contains all
              event records that are publically viewable.

       /var/evlog/privatelog
              Privatelog  is a secondary system log that contains
              records you generally don't want to  be  publically
              viewable.   By  default,  only  event  records with
              facility of AUTHPRIV are written to this log.  How­
              ever,  events  from  other  facilities  can also be
              written to this log, as specified with  the  evlfa­
              cility  command.  An example of private records are
              those associated with port connections for services
              running on a system.

       In addition to letting you create and maintain logs, event
       logging provides you  the  ability  to  be  notified  when
       events  of interest to you occur and lets you specify what
       actions you want to execute automatically in  response  to
       those events.


COMMANDS

       evlview(1)
              Lets  you  display event records from a POSIX-stan­
              dard event log. evlview gives you many options  for
              selecting what records you view and for designating
              what format to use in displaying those records.

       evlfacility(1)
              Lets you register and list facilities defined for a
              system.   Facilities are simply the components of a
              system  that  issue  event   records.    Facilities
              include  the kernel, device drivers, services, such
              as mail,  cron  and  ftp,  and  user  applications.
              Event  log  facilities include, but are not limited
              to,  facilities  defined  for  syslog.  evlfacility
              ensures  that  facilities you register are uniquely
              identified across systems.

       evlnotify(1)
       evltc(1)
              Compiles  formatting  templates  containing  C-like
              structures used for parsing  and  displaying  event
              data, for example by the evlview command.

       evlogmgr(1)
              Lets  you  perform log management on the event log,
              on the private log, or optionally, on  a  log  file
              that you  specify.  You specify which events are to
              be deleted. The space freed by  deleted  events  is
              reused  for undeleted events (a process referred to
              as compaction) and the log file is truncated,  thus
              reducing its overall size.

       evlsend(1)
              Lets   you  send  event  records  from  scripts  or
              directly from a command line.


QUERIES

       The commands evlview, evlnotify, evlconfig,  and  evlogmgr
       let you specify a query or filter to describe the kinds of
       events in which you are interested.  For details of how to
       specify queries, see evlquery(1).


DAEMONS

       /sbin/evlogd
              The  event  log  daemon  reads  event  records from
              facilities running in the kernel and in user  space
              and  writes  those records to the appropriate local
              POSIX-standard log  file.   Additionally,  plug-ins
              can  be  provided  that  register  with  evlogd  to
              receive the event stream  and  provide  alternative
              methods of processing and logging the events.

              2  plug-ins  are  provided  with  the event logging
              package: the   udp_rmtlog_be  plugin  and  tcp_rmt­
              log_be plugin which forward events to a centralized
              event  consolidation  host,  using  UDP  and   TCP,
              respectively.

       /sbin/evlogrmtd
              The remote event daemon receives event records from
              other hosts on the network  that  are  transmitting
              with  the   udp_rmtlog_be  or tcp_rmtlog_be plugin,
              and  if  the  source  host   is   listed   in   the
              /etc/evlog.d/evlhosts file, passes the event record
              to the evlogd.   Otherwise,  the  event  record  is
              rejected and discarded by the evlogrmtd.

       /sbin/evlnotifyd
              The  event notification daemon accepts notification
              requests from client processes, reads event records

                         6 December 2002                  EVLOG()

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =


  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can help in many different ways.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.05 Seconds