Process and apparatus for managing a software load image

• US 5,991,544 A
• Filed: 12/09/1997
• Issued: 11/23/1999
• Est. Priority Date: 12/09/1997
• Status: Expired due to Term

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Corporation
• Inventors: Godse, Dhananjay
• Primary Examiner(s): Hafiz, Tariq R.
• Assistant Examiner(s): ZHEN, WEI Y
• Application Number:
  US08/987,251
• Time in Patent Office: 714 Days
• Field of Search: 395/712
• US Class Current: 717/167
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Abstract

The present invention relates to a method and apparatus to permit a computer to manage its software load image. This operation takes place when the computer powers on and when a new software sub-system is dynamically loaded into an address space where a software load is already running. During the booting procedure, after the operating system has been initialized, software sub-systems are started. Typically the linker-loader module of the operating system resolves symbol references for each sub-system, allocates memory and then starts the sub-systems. The novel method involves the additional step of registering the sub-system in an in-memory location, herein designated as load description database, before starting the sub-system. Similarly, when a sub-system is removed from a computer, it registers with the load description database indicating that it has been removed. The result is that the load description database always reflects the sub-systems present on the computer at any given time. The invention also provides a machine-readable medium comprising a program element to implement the load image management process.

Claims

1. A machine-readable storage medium comprising a program element for execution by a computer node for managing a software load image of the computer node, said machine readable medium comprising:

a) a first data structure forming a symbol table for holding at least one entry constituting a registration trigger associated to a software entity;

b) a second data structure forming a load description database for holding a plurality of entries indicative of respective software entities executed on the computer node, whereby an entity external to the computer node can query said load description database to obtain the software load image of the computing node;

c) the program element being operative for;

i) processing said symbol table to locate a registration trigger;

ii) in response to location of a registration trigger creating an entry in said load description database, the entry created in said load description database being indicative that the software entity associated with the registration trigger is being executed on the computer node;

iii) causing execution of the software entity.

2. A machine-readable storage medium as defined in claim 1, wherein said program element forms part of a loader.

3. A machine-readable storage medium as defined in claim 2, wherein said registration trigger includes a predetermined string of characters.

4. A machine-readable storage medium as defined in claim 3, wherein said loader provides means to process entries in said symbol table to search for said pre-determined string of characters, upon identification of said predetermined string of characters said program element in said loader causing the creation of the entry in said load description database.

5. A machine-readable storage medium as defined in claim 4, wherein the entry created in said load-description database includes a first identifier indicative of a procedure associated to said software entity that when invoked terminates said software entity.

6. A machine-readable storage medium as defined in claim 5, wherein the entry created in said load-description database includes a second identifier indicative of a procedure associated to said software entity that when invoked activates said software entity.

7. A machine-readable storage medium as defined in claim 6, wherein said load-description database is a file.

8. A machine-readable storage medium as defined in claim 1, wherein the machine-readable storage medium is the RAM of a computing apparatus.

9. A method for managing a software load image of a computer node including a memory in which resides a first data structure forming a symbol table for holding at least one entry constituting a registration trigger associated to a software entity, said symbol table being associated with at least one software entity, said method comprising;

invoking a linker to process said symbol table to locate a registration trigger;

on location of said registration trigger creating an entry in a load description database, whereby an entity external to the computing node can query said load description database to obtain the software load image of the computing node, the entry created in the load description database being indicative that the software entity associated with the registration trigger is being executed on the computer node;

causing execution of the software entity.

10. A method as defined in claim 9, wherein said registration trigger includes a predetermined string of characters.

11. A method as defined in claim 10, wherein the entry created in said load-description database includes a first identifier indicative of a procedure associated to said software entity that when invoked terminates said software entity.

12. A method as defined in claim 11, wherein the entry created in said load-description database includes a second identifier indicative of a procedure associated to said software entity that when invoked activates said software entity.

13. A method as defined in claim 12, wherein said load-description database is a file.

14. In combination:

a) a first computing node;

b) a second computing node in a data communicative relationship with said first computing node, said second computing node including a machine-readable storage medium comprising a program element for execution by the second computing node for managing a software load image of the second computing node, said computer readable storage medium comprising;

i) a first data structure forming a symbol table for holding at least one entry constituting a registration trigger associated to a software entity;

ii) a second data structure forming a load description database for holding a plurality of entries indicative of respective software entities executed on the second computing node, whereby an entity external to the second computing node can guery said load description database to obtain the software load image of the second computing node;

iii) the program element being operative for;

processing said symbol table to locate a registration trigger;

in response to location of a registration trigger creating an entry in said load description database, the entry created in said load description database being indicative that the software entity associated with the registration trigger is being executed on the second computing node;

causing execution of the software entity on said second computing node;

said second computing node being responsive to a message from said first computing node to transmit to said first computing node data originating from said second data structure.

15. A computing apparatus for managing a software load image of a computer node, said apparatus comprising a memory including:

a) a first data structure forming a symbol table for holding at least one entry constituting a registration trigger associated to a software entity;

b) a second data structure forming a load description database for holding a plurality of entries indicative of respective software entities executed on the computer node, whereby an entity external to the computer node can query said load description database to obtain the software load image of the computer node;

c) the program element being operative for;

i) processing said symbol table to locate a registration trigger;

ii) in response to location of a registration trigger creating an entry in said load description database, the entry created in said load description database being indicative that the software entity associated with the registration trigger is being executed on the computer node;

iii) causing execution of the software entity.

16. An apparatus as defined in claim 15, wherein said application program element forms part of a loader.

17. An apparatus as defined in claim 16, wherein said registration trigger includes a predetermined string of characters.

18. An apparatus as defined in claim 17, wherein said loader is operative to process entries in said symbol table to search for said pre-determined string of characters, upon identification of said predetermined string of characters said program element in said loader causing the creation of the entry in said load description database.

19. An apparatus as defined in claim 18, wherein the entry created in said load-description database includes a first identifier indicative of a procedure associated to said software entity that when invoked terminates said software entity.

20. An apparatus as defined in claim 19, wherein the entry created in said load-description database includes a second identifier indicative of a procedure associated to said software entity that when invoked activates said software entity.

21. An apparatus as defined in claim 20, wherein said load-description database is a file.

22. An apparatus as defined in claim 15, wherein said memory is the RAM of a computing apparatus.