home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!darkstar.UCSC.EDU!osr
- From: moss@cs.cmu.edu (Eliot Moss)
- Newsgroups: comp.os.research
- Subject: Re: Looking for information on the use of logging
- Date: 16 Nov 1992 21:12:05 GMT
- Organization: Dept of Comp and Info Sci, Univ of Mass (Amherst)
- Lines: 26
- Approved: comp-os-research@ftp.cse.ucsc.edu
- Message-ID: <1e92r5INN8db@darkstar.UCSC.EDU>
- References: <1e1pjiINN532@darkstar.UCSC.EDU>
- NNTP-Posting-Host: ftp.cse.ucsc.edu
- Originator: osr@ftp
-
- Let's pop up a level here: logging is one way of recording information for
- possible use after a crash. Note ONE way -- there are other ways. Logging has
- appeal in that it generally leads to sequential writes, both within a log
- flush and across them (since the disk head (or whatever) stays in the same
- region), giving higher performance in the sense of shorter latency. Another
- feature of logging is that it maintains order, which means that one can
- consider logging ACTIONS rather than just DATA. Some of the cases you mention
- I am not sure I would call logging, but are event recording (tracing and
- monitoring); I make the distinction based more on the use of the information,
- not the general notion that a log is a sequential record of some stuff that
- happened.
-
- Any application that can benefit from these features could use logging. One
- thing that you missed is editors that log keystrokes or buffer changes. Hope
- this helps ...
- --
-
- J. Eliot B. Moss, Associate Professor Visiting Associate Professor
- Department of Computer Science School of Computer Science
- Lederle Graduate Research Center Carnegie Mellon University
- University of Massachusetts 5000 Forbes Avenue
- Amherst, MA 01003 Pittsburgh, PA 15213-3891
- (413) 545-4206, 545-1249 (fax) (412) 268-6767, 681-5739 (fax)
- Moss@cs.umass.edu Moss@cs.cmu.edu
-
-
-