Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Let The Music Play: Join EFF Today

 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

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

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

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




       evlgentmpls directory object-file ...


       For each object-file, evlgentmpls reads the  .log  section
       (if  any)  and generates a template specification for each
       event-logging call described therein.

       All template specifications for the facility whose canoni­
       cal name is facname are appended to directory/facname/fac­
       name.t.  directory, directory/facname, and  facname.t  are
       all  created  if  they  do  not  already  exist.  Multiple
       object-files can yield  template  specifications  for  the
       same  facility.  Each facname.t file can be compiled using

       A canonical facility name is created by converting  upper­
       case  ASCII  letters  to lowercase, spaces to underscores,
       and all other ASCII punctuation characters to periods.

       object-file may be relocatable (.o),  executable  (a.out),
       or a library (.a or .so).

       When  you compile a C file containing calls to syslogat(),
       information about each call is recorded in the  .log  sec­
       tion  of  the  resulting  object  file.   This information
       includes the names of the source file  and  calling  func­
       tion, plus the syslogat() format string (which may specify
       attribute names for the values logged).  You can then  use
       evlgentmpls  to  create the template source file(s) corre­
       sponding to those calls, and evltc to compile the template
       source file(s).  Once you have installed the resulting .to
       files (typically  in  /var/evlog/templates),  evlview  and
       other  libevl-based  programs can use those templates when
       examining events logged by your program.

       evlgentmpls can also be applied to kernel object files  --
       for  example,  files  that  contain  calls to the proposed
       printkat() macro.

       To strip the .log section out of an object file after  you
       have run evlgentmpls, use "objcopy -R .log objfile".


       Suppose raidmon.c contains the following lines:

       #define EVL_FACILITY_NAME raidmon
            "Fan #{fan}%d has been shut down; {ngoodfans}%d fans remaining.0,
            badfan->id, ngoodfans);

       # evltc /var/evlog/templates/raidmon/raidmon.t

       compiles  raidmon.t  and  generates a binary template (.to
       file) for each syslogat() call.

       With these templates in place, a command such as

       $ evlview -b -f 'ngoodfans < 3'

       can be used to find records such as the one logged by  the
       aforementioned syslogat() call.


       evltc(1), evlview(1)

                         18 December 2002          EVLGENTMPLS(1)

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


More information about the site can be found in the FAQ



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?
The Linux Tutorial can use your help.


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.09 Seconds