Independent log manager

• US 20020165902A1
• Filed: 05/03/2001
• Published: 11/07/2002
• Est. Priority Date: 05/03/2001
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Scheetz, Michael, Robb, Mary Thomas, Sanchez, Humberto A. II
• Application Number:
  US09/848,711
• Publication Number:
  US 20020165902A1
• Time in Patent Office: Days
• US Class Current: 709/202
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

A method and apparatus of logging events independently and separately from other processes in a computer system are disclosed. A method for logging events by cloning a log entry submitted by a consumer and releasing control of the log entry to the consumer so that execution of an event may continue is disclosed. A log manager that receives requests for writing event log entries to a log file while enabling the execution of the event to continue independently is disclosed.

Claims

1. A method for logging events independently and separately from other processes in a computer system, comprising:

initiating an event, wherein the event is a process executed on a computer system;

creating a log entry, wherein the log entry comprises information that describes the event;

requesting that the log entry information be written to a log file, whereby the consumer surrenders control of the log entry, pausing execution of the event; and

releasing control of the log entry to the consumer, so that execution of the event can resume, prior to writing the log entry information to the log file, wherein releasing control of the log entry to the consumer comprises;

cloning the log entry, wherein the log entry clone is a copy of the log entry that comprises the log entry information.

2. The method of claim 1, wherein the cloning step is performed by a multiple-threaded log manager.

3. The method of claim 1, further comprising:

queuing the log entry clone in a queue that determines when the log entry information is written to the log file.

4. The method of claim 3, wherein the queue is a first in, first out queue.

5. The method of claim 3, wherein at some time the log entry clone has a turn, the method further comprising:

determining if the log entry clone is next in the queue; and

,

if the log entry clone is next in the queue, writing the log entry information to log file.

6. The method of claim 1, wherein the log entry is an object comprising attributes populated with the log entry information.

7. The method of claim 1, wherein the event is a configuration event.

8. The method of claim 1, wherein the consumer is a client.

9. The method of claim 1, wherein the event is a task event, the method further comprising:

starting a log transaction, wherein starting a log transaction comprises a consumer sending a message that a sequence of related task log entries are to be sent.

10. The method of claim 9, further comprising

determining if the task event has ended, wherein the end of the task event comprises the completion of the task event or a failure to complete the task event;

and,

if the task event has ended, terminating the log transaction, wherein terminating the log transaction indicates that a sequence of log entries associated with the task event has ended and that the log file may be rolled-over without interrupting logging of the task event.

11. The method of claim 9, wherein the consumer is a task manager.

13. The computer readable medium of claim 12, wherein releasing control of the log entry to the consumer comprises:

cloning the log entry, wherein the log entry clone is a copy of the log entry that comprises the log entry information.

14. The computer readable medium of claim 13, further comprising instructions for logging events entries independently and separately from other processes in a computer system, by:

queuing the log entry clone in a queue that determines when the log entry information is written to the log file.

15. The computer readable medium of claim 14, wherein the log entry clone has a turn, further comprising instructions for logging events entries independently and separately from other processes in a computer system, by:

determining if the log entry clone is next in the queue; and

,

if the log entry clone is next in the queue, writing the log entry information to log file.

16. The computer readable medium of claim 12, wherein the log entry is an object comprising attributes populated with the log entry information.

18. The computer system of claim 17, wherein releasing control of the log entry to the consumer comprises:

the log manager cloning the log entry, wherein the log entry clone is a copy of the log entry that comprises the log entry information.

19. The computer system of claim 17, wherein the consumer is a task manager.

20. The computer system of claim 17, wherein the log entry is an object that comprises attributes which are populated with the log entry information.

12. A computer readable medium containing instructions for logging events independently and separately from other processes in a computer system, by:

a consumer initiating an event, wherein the event is a process executed on a computer system;

creating a log entry, wherein the log entry comprises information that describes the event;

requesting that the log entry information be written to a log file, whereby the consumer surrenders control of the log entry, pausing execution of the event; and

,

releasing control of the log entry to the consumer, so that execution of the event can resume, prior to writing the log entry information to the log file.

17. A computer system that supports logging events independently and separately from other processes in a computer system, comprising:

a memory, that stores an application;

a secondary storage device comprising a log file;

a processor that runs the application, wherein the application comprises;

a consumer, wherein the consumer initiates an event that is a process executed by the processor, creates a log entry comprising information that describes the event, and requests that the log entry information be written to the log file;

a multiple-threaded log manager, wherein the log manager, independently and separately from other processes, logs events, by;

receiving the log entry from the consumer, thereby obtaining control of the log entry and pausing execution of the event; and

,

releasing control of the log entry to the consumer, so that execution of the event can resume, prior to writing the log entry information to the log file.