By James D. Murray Publisher: O'Reilly Media Released: September 1998 Pages: 320
Event logging is a facility used by computer systems to record the occurrence of significant events. An "event" is any change that occurs in a system -- for example, a user logon, an addition to a file, or a change to a user's privileges. Because a computer system may experience hundreds or thousands of events each second, it is important to distinguish which events require the immediate attention of a system administrator, which should be recorded as entries in the system's event log for later analysis, and which can be safely ignored. Event logs provide a centralized collection point for all kinds of error reports, system alerts, diagnostic messages, and status messages generated by a system. This book describes the characteristics of these messages, why they are important, and how you can access them and act upon them. Event logs are particularly important to system security and problem troubleshooting. Windows NT systems generate three distinct types of event logs: - Security log. Stores reports of security-related events -- for example, a user has written to a file or there has been a change in a user's privileges.
- System log. Stores reports generated by system components, including drivers and services -- for example, a device failed, a driver failed to load, or a memory allocation or I/O error occurred.
- Application log. Stores reports on all other events -- for example, an internal application error (such as a failure to allocate memory) occurred, or a file download aborted.
This book is aimed at several specific audiences: For system administrators, event logging is a tool for analyzing system and user activities and performance and for troubleshooting system problems. For this audience, the book explains how to view and maintain the event logs via the system's Event Viewer and how to interpret the results. For programmers, event logging helps in diagnosing system or network problems. For this audience, the book describes the event logging API (Application Programming Interface) and the internals of the system's message files. It also provides instructions for and examples of accessing (reading, backing up, clearing, monitoring, and writing to) the event logs from C, Visual Basic 5, Perl 5 for Win32, Visual J++, and a C++ class for MFC (Microsoft Foundation Classes). For security administrators, event logging is an important tool in auditing security-related events and tracking down the source of security breaches. For this audience, the book provides help in specifying the events to be audited and in analyzing auditing results; it also discusses the security auditing requirements imposed on a C2-level secure system (one approved by the U.S. government's National Computer Security Center). The book comes with a CD-ROM containing examples from the book and many contributed event logging and auditing software packages. A brief table of contents follows: Preface 1. About Event Logging2. The Event Logging Service3. Even Viewer 4. Windows NT Security Auditing 5. The Event Logging API6. Message Files7. Accessing the Event Logs8. Reporting Events A. References and ResourcesB. Event Logging under Windows for WorkgroupsC. NT Security Auditing Events D. DumpEl: Event Logging Dump UtilityE. Kernel-mode Event LoggingF. What's on the CD-ROM? |
- Title:
- Windows NT Event Logging
- By:
- James D. Murray
- Publisher:
- O'Reilly Media
- Formats:
-
- Print:
- September 1998
- Pages:
- 320
- Print ISBN:
- 978-1-56592-514-4
- | ISBN 10:
- 1-56592-514-9
|
Colophon Our look is the result of reader comments, our own experimentation, and feedback from distribution channels. Distinctive covers complement our distinctive approach to technical topics, breathing personality and life into potentially dry subjects. The animal appearing on the cover of Windows NT Event Logging is a North American beaver (Castor canadensis), a large, nocturnal, primarily aquatic rodent found throughout most of North America, excluding the southernmost areas. Beavers grow up to 35-40 inches in length and weigh from 30-60 pounds. Like all rodents, beavers' teeth grow continually, so they must be trimmed by gnawing on bark, wood, or other material. Their diet consists of wood, bark, buds, roots, and underwater vegetation; beavers, unlike mammals, have the ability to digest cellulose. Both sexes have waterproof, dark brown fur, webbed hind feet, and a scaly, horizontally flat, broad tail; it is difficult to distinguish between males and females. They can remain submerged for minutes at a time. Beavers mature sexually at around 2-3 years old; they form monogamous pairs, and, after a gestation period of about three months, produce fully furred, toothed, and open-eyed young (known as kits) in litters of around four. The offspring stay with their parents for one or two years, frequently assisting with successive litters as well as the usual food gathering, and then form their own families. Their lifespan ranges from 10-20 years. Beavers are territorial and attempt to scare off perceived threats with loud slaps of their broad tails on the surface of the water. Emerging at dusk, beavers build highly complex and intelligently engineered dams to block the flow of water in the streams and rivers in which they live. They live in colonies of up to eight beavers in large, warm lodges made of sticks, mud, and rocks, with underwater entrances. Beavers travel great distances for food, if necessary, and will also build intricate canal systems in order to float food back to their lodge. In the winter, they mostly stay in or near the lodge, under the ice, having stockpiled food and body fat in advance. Their effect on the environment is both positive and negative; while their lumberjack activities create habitats for many other animals and plant life, they also tend to destroy one pond or former stream and then, as it fills up with silt, move on to another. Once endangered by overzealous trapping, beavers are now widespread and common in many areas. Their greatest threat today is the expansion of human civilization and habitat destruction. Jane Ellin was the production editor of Windows NT Event Logging. Ellie Maden was the copyeditor; Seth Maislin wrote the index; Sheryl Avruch, Claire Cloutier LeBlanc, and Clairemarie Fisher O'Leary provided quality control; and Sebastian Banker, Kimo Carter, and Trisha Manoni provided production support. Edie Freedman designed the cover of this book, using an original illustration purchased in Paris from a kiosk on the Seine in the Fall of 1997 (illustrator unknown); Hanna Dyer designed the CD label. The cover layout was produced with QuarkXPress 3.32 using the ITC Garamond font. Whenever possible, our books use either RepKover(TM), a durable and flexible lay-flat binding, or Otabind(TM). If the page count exceeds the maximum bulk possible for this type of binding, perfect binding is used. The inside layout was designed by Nancy Priest and implemented in FrameMaker 5.5 by Mike Sierra. The text and heading fonts are ITC Garamond Light and Garamond Book. The illustrations that appear in the book were created in Adobe Photoshop 4 by Robert Romano. This colophon was written by Nancy Kotary. |
|
Description
|
Product Details
|
Colophon
|
 |
|
 |
|
|
|
Recommended for You
|
Recently Viewed
|
 |
|
By Debbie Poyser, Derek Johnson
May 2005
By Carl Malamud
June 1993
|
Customer Reviews
5/24/2000 (0 of 2 customers found this review helpful) 1.0Windows NT Event Logging Review
|
|
|