Transparent fast application launcher

• US 10,310,872 B2
• Filed: 02/21/2017
• Issued: 06/04/2019
• Est. Priority Date: 02/21/2017
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Tsirkin, Michael
• Primary Examiner(s): Lyons, Andrew M.
• Application Number:
  US15/438,086
• Publication Number:
  US 20180239620A1
• Time in Patent Office: 833 Days
• Field of Search: 717162-164, 718 1
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

Methods and apparatus for a transparent fast application launcher are disclosed. For example, an executable loader receives a first request to load and then loads a first copy of an executable program into a memory, including resolving and loading at least one shared library associated with the executable program to the memory. A local socket is associated with the first copy of the executable program. An entry indicative of the local socket and the first executable program is recorded in an executable database. The executable loader receives a second request to load a second copy of the executable program and then connects to the local socket as a client to send a third request to the local socket based on the second request to launch the second copy of the executable program, resulting in the second copy of the executable program executing.

Claims

1. A system comprising:

a memory;

an executable database stored in the memory, wherein the executable database is associated with a plurality of executable programs including the first executable program, each executable program of the plurality of executable programs respectively having an associated entry in the executable database including a first associated entry associated with the first executable program;

one or more processors;

an executable loader executing on the one or more processors to;

receive a first request to load a first copy of a first executable program;

responsive to receiving the first request, load the first copy of the first executable program into the memory, including;

resolving at least one shared library associated with the first executable program; and

loading the at least one shared library associated with the first executable program to the memory;

associate a local socket with the first copy of the first executable program;

record an entry indicative of the local socket and the first executable program in the executable database;

receive a second request to load a second copy of the first executable program;

connect to the local socket as a client; and

send a third request based on the second request to launch the second copy of the first executable program to the local socket, wherein the second copy of the first executable program executes responsive to the local socket receiving the third request, wherein the executable database is periodically purged, the first associated entry is purged independently of each other entry, purging the first associated entry triggers the termination of the first executable program, and a change to a binary file associated with the first executable program of the plurality of executable programs triggers purging of the first associated entry.

2. The system of claim 1, wherein the first copy of the first executable program acts as a server rather than executing operationally.

3. The system of claim 1, wherein the second request includes at least one of an argument value and an environment value passed to the second copy of the first executable program and the second copy of the first executable program is launched with the at least one of an argument value and an environment value.

4. The system of claim 1, wherein the second copy of the first executable program is one of cloned and forked from the first copy of the first executable program.

5. The system of claim 1, wherein a purging of the executable database is triggered based on at least one of an elapsed time, a memory usage, and a quantity of requests sent to the first copy of the first executable program.

6. The system of claim 1, wherein the executable loader determines that the second request is a request to launch a second copy of the first executable program based on at least one of an executable path, an environment value, and security attributes.

7. The system of claim 1, wherein the first request and the second request are parts of a same request message.

8. The system of claim 1, wherein the first request is implied from a receipt of the second request where the first copy of the first executable program is unlaunched.

9. The system of claim 1, wherein the first request includes operational execution instructions, and after launching the first copy of the first executable program, the executable loader converts the operational execution instructions into a fourth request to launch a third copy of the first executable program to execute operationally the operational execution instructions.

10. The system of claim 9, wherein the operational execution instructions are one of a command line input, a file input, a queue input, and an environment value.

11. The system of claim 1, wherein the entry in the executable database includes user specific information and the second copy of the first executable program is launched with settings based on the user specific information.

12. The system of claim 1, wherein the entry in the executable database includes environment values of the first executable program.

13. The system of claim 1, wherein the at least one shared library associated with the first executable program is initialized prior to the second copy of the first executable program being launched.

14. The system of claim 1, wherein the at least one shared library associated with the first executable program is initialized based on an environment value associated with the second copy of the first executable program.

15. A method comprising:

receiving, by an executable loader, a first request to load a first copy of a first executable program;

responsive to receiving the first request, loading the first copy of the first executable program into a memory, including;

resolving at least one shared library associated with the first executable program; and

loading the at least one shared library associated with the first executable program to the memory;

associating a local socket with the first copy of the first executable program;

recording an entry indicative of the local socket and the first executable program in an executable database, wherein the first request includes operational execution instructions that are one of a command line input, a file input, a queue input, and an environment value, and after launching the first copy of the first executable program, the executable loader converts the operational execution instructions into a second request to launch a second copy of the first executable program to execute operationally the operational execution instructions;

receiving a third request to load a third copy of the first executable program;

connecting to the local socket as a client; and

sending a fourth request based on the third request to launch the third copy of the first executable program to the local socket, wherein the third copy of the first executable program executes responsive to the local socket receiving the fourth request.

16. The method of claim 15, wherein the first copy of the first executable program acts as a server rather than executing operationally.

17. The method of claim 15, further comprising:

one of cloning and forking the first copy of the first executable program to launch the second copy of the first executable program.

18. The method of claim 15, wherein the executable database is associated with a plurality of executable programs including the first executable program, each executable program of the plurality of executable programs respectively having an associated entry in the executable database including a first associated entry associated with the first executable program, the method further comprising:

periodically purging the executable database, wherein purging the first associated entry triggers the termination of the first executable program, and a change to a binary file associated with the first executable program of the plurality of executable programs triggers purging of the first associated entry.

19. The method of claim 15, wherein the first request is implied from a receipt of the second request where the first copy of the first executable program is unlaunched.

20. A computer-readable non-transitory storage medium storing executable instructions, which when executed by a computer system, cause the computer system to:

receive, by an executable loader, a first request to load a first copy of a first executable program;

responsive to receiving the first request, load the first copy of the first executable program into a memory, including;

resolving at least one shared library associated with the first executable program; and

loading the at least one shared library associated with the first executable program to the memory;

associate a local socket with the first copy of the first executable program;

record an entry indicative of the local socket and the first executable program in an executable database, wherein the first request includes operational execution instructions, the operational execution instructions are one of a command line input, a file input, a queue input, and an environment value, and after launching the first copy of the first executable program, the executable loader converts the operational execution instructions into a second request to launch a second copy of the first executable program to execute operationally the operational execution instructions;

receive a third request to load a third copy of the first executable program;

connect to the local socket as a client; and

send a third fourth request based on the third request to launch the third copy of the first executable program to the local socket, wherein the third copy of the first executable program executes responsive to the local socket receiving the fourth request.