JPH0830347A - Automatic starting device - Google Patents

Abstract

PURPOSE:To automate the start/end processing of a user process or the like and to easily perform change it corresponding to the purpose of use by automatically starting the processes, which are set in a user processing register file, at prescribed time intervals. CONSTITUTION:A user processing register file 5 is provided to previously register plural process names, time and right and the information required for controlling processes is set in a control table 3. After the lapse of set time from the start of a process (user process) 4 equipped with the process name extracted from the user processing register file 5, a process preparing means 2 repeats the extraction of the next process name and the start of that process or applies the right set to the started process. Thus, the start/end processing of the user process of a computer 1 or the like can be automated, and the user process to be started at the time of start or end, the order or the time interval can be easily changed corresponding to the purpose of use.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a process automatic starting device.

[0002]

2. Description of the Related Art Conventionally, a computer, when the power is turned on, loads the system from the external storage device to the main storage device and performs various initializations, starts up the system so that it can be used, and then specifies it in advance. The user process was uniquely activated so that the actual operation could be started.
In addition, at the time of termination, a user process designated in advance is uniquely activated to perform termination processing, and then the power is shut down.

[0003]

Therefore, when the computer is started, the appropriate processes are sequentially started in the appropriate order at the appropriate time intervals, and at the end, the appropriate processes are appropriately started in the appropriate order. There is a problem that it is not possible to shut down the power after sequentially starting and ending at different time intervals and changing the order and time interval of these starting processes arbitrarily and easily according to the customer's application. .

The present invention solves these problems.
A user process registration file is provided to automatically start the processes set in the user process registration file at the time of starting or ending the computer in the set order and at the time interval set and with the set privileges. However, the purpose is to automate the start-up processing and termination processing of the user process of the computer and to make it easy to change according to the application.

[0005]

FIG. 1 shows a block diagram of the principle of the present invention. In FIG. 1, a computer 1 activates a user process to perform various processes, and is composed of a process creating unit 2, a control table 3, a user process 4, and the like.

After the process having the process name (user process 4) fetched from the user process registration file 5 is started, the process creating means 2 fetches the next process name after the set time elapses and executes the process. The activation is repeated, and the authority (execution UID) set in the activated process is given.

The control table 3 is for setting information necessary for controlling the process. The user process 4 is a started process and is a process for performing various tasks.

The user process registration file 5 is for registering a process name, time and authority (execution UID). The status file 6 sets and saves an end flag and the like.

The power controller 7 turns on the power of the computer 1.
/ OFF.

[0010]

According to the present invention, as shown in FIG. 1, after the process creation means 2 starts the process having the process name of the user process registration file 5, the process having the next process name is executed after the preset time elapses. The process is repeated by starting up.

Further, the process creating means 2 creates the process with the authority of the process having the process name of the user process registration file 5 as the registered authority, and activates and executes the process.

Therefore, the user process registration file 5 is provided to set the processes set in the user process registration file 5 in the set order at the time of starting or ending the user process of the computer 1. It is possible to automate the startup process and termination process of the user process of the computer 1 by giving the authority that was automatically started and set at intervals, and easily change it according to the purpose. It is possible to grant arbitrary authority for each.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

FIG. 2 shows a flowchart for explaining the overall operation of the present invention. This is a flowchart for explaining the overall operation of the configuration of FIG. In FIG. 2, S1 is a user process registration. This is to register the waiting time until the next process start and the process execution UID (process authority) in association with the process name, as shown in the user process registration file 5 of FIG. To do. This allows
This means that the user can previously register the user process registration file 5 to be used at the time of normal startup or at the time of normal termination.

In step S2, a user process activation request is accepted. In S3, the end flag is read from the status file 6. This is the computer 1 as shown in FIG.
At the end of, the state at that time was set and saved in the end flag 61, so the end flag 61 is read,
Recognize the state at the end of the computer 1. For example, it recognizes a state in which it is finished in response to an end request or is finished in response to a power failure. The startup process is performed using the user process registration file 5 corresponding to the state at the end of the computer 1.

In step S4, the process corresponding to the end flag is read. This is performed by selecting the user processing registration file 5 corresponding to the state (the state such as ending in response to an end request and ending in response to a power failure) found by the end flag 61 read in S3, and the selected use The user process registration file 5 is read.

In step S5, the user process 1 is activated. This starts the user process 1 by taking out the user process 1 from the head of the user process registration file 5 read in S4. At the time of this startup, the system account (the authority that the system has,
All normal resources can be used) and start process is executed.

In step S6, the execution UID of the process is changed. This takes out the execution UID (authority) corresponding to the process set in the user process registration file 5,
It is given to the started process and the usable resources are limited. As a result, the activated process independently executes the process using the resource under the authority of the execution UID.

S7 is the next step S after the lapse of t1 seconds.
Proceed to 8. This proceeds to S8 to activate the next process after the time t1 set in the user process registration file 5 has elapsed.

In step S8, it is determined whether it is the final process. Yes
In the case of, since the start of all the processes has finished, S
Operation starts at 9. On the other hand, in the case of NO, since it is determined that all the processes are not activated, the process returns to S5 and is repeated, and the process of activating the next process registered in the user process registration file 5 and assigning the execution UID are repeated. .

Through the above steps S2 to S9, the user process registration file 5 corresponding to the end state found from the end flag 61 read from the status file 6 is read in response to the user process activation instruction, and the user process registration file 5 is used. Sequential startup and execution U from the first process of the user process registration file 5
All processes are started by repeating the process of assigning an ID, activating the next process after the elapse of the set time, and assigning the execution UID. With these, process activation, execution U is automatically performed only by simple operation of setting the process name, time, and execution UID in the user process registration file 5.
ID (authority) is given, next process is started after a lapse of time,
Execution UDI (authority) can be repeatedly given, and any process can be automatically started by setting any time interval, any privilege, etc. in any combination according to the end user's application. It became possible to launch the user process of.

In step S10, a user processing end request is accepted. In step S11, the process corresponding to the end request is read. In S10, the user processing registration file 5 is selected according to the status corresponding to the termination request (normal termination request, termination request corresponding to power failure, etc.), and the selected user processing registration file 5 is read.

In step S12, the user process 1 is activated.
This is the user process registration file 5 read in S11.
The user process 1 is taken out from the beginning of and is started. At the time of this activation, the activation process is executed with the system account (privileges possessed by the system, all normal resources can be used).

In step S13, the execution UID of the process is changed. This takes out the execution UID (authority) corresponding to the process set in the user process registration file 5,
It is given to the started process and the usable resources are limited. As a result, the activated process independently executes the process using the resource under the authority of the execution UID.

In S14, after t1 seconds have elapsed, the process proceeds to S15 of the next step. This proceeds to S15 to activate the next process after the time t1 set in the user process registration file 5 has elapsed.

In step S15, it is determined whether it is the final process. YE
In the case of S, since the start of all processes has been completed,
The power supply is shut down in S16. On the other hand, in the case of NO, since it is determined that all the processes have not been activated, the process returns to S12 and is repeated, and the user process registration file 5
The next process registered in is started and the execution UID is given repeatedly.

By the above S10 to S16, in response to the user processing end request, the end request (normal end request,
The user process registration file 5 corresponding to a termination request due to a power outage, etc. is read, the processes are sequentially started from the first process of the user process registration file 5, an execution UID is given, and the next process is started after the set time elapses. , Run UI
The process of giving D is repeated to start all processes. With these, the process start, the execution UID (authority) is automatically given, and the next process is started and executed after a lapse of time by only a simple operation of setting the process name, time, and execution UID in the user process registration file 5. It becomes possible to repeat the assignment of UID (authority) and at the same time, according to the end user's use, any process can be automatically started by setting any time interval and authority in any combination and using the computer 1. It has become possible to execute the termination process of the user process and shut down.

FIG. 3 shows an example of the user processing registration file of the present invention. FIG. 3A shows an example of the user processing registration file 5 at the time of normal startup. This is an example of the user process registration file 5 read in S4 when the user registration file 5 for normal startup is selected from the state of the end flag 61 read in S3 of FIG. In the user process registration file 5 at the time of normal startup, as shown in the figure, the process name, the waiting time t until the next process is started, and the process execution UID are registered as a set and registered in the order of starting. Here, the process name represents the name of the process to be activated. The waiting time t until the start of the next process represents the time interval t until the start of the next process. The process execution UID represents the authority (execution UID) given to the activated process. When starting a process, the process creating means 2 uses the system's authority (usually has the authority to use all resources) to secure necessary resources (for example, to secure memory) and activate the process. An execution UID is given to the started process. The process started by being given this execution UID secures resources and accesses the database using the authority determined by the execution UID. This limits the resources available to the started process.

FIG. 3B shows an example of the user process registration file 5 at the normal end. This is the case where the content of the end request in S10 of FIG. 2 is "normal end". In the user process registration file 5 at the time of normal termination, as shown in the figure: -Process name-Wait time t until the next process is started-Process execution UIDs are registered as a set in the starting order, and Presence / absence of shutdown execution ・ Time interval T until system stop ・ Register other. Here, the process name, the waiting time t until the start of the next process, and the process execution UID are the same as those in FIG. The presence / absence of shutdown is whether or not to shut down (power off) after sequentially executing all the processes. The time interval T until the system is stopped is the time interval until the system is stopped after starting all the processes, and a value with a slight allowance for the time to finish the execution of the termination processing by the process is registered. .

FIG. 4 shows an example of the status file of the present invention. In this status file 6, an end flag 61 is registered and saved as shown in the figure, and the end state immediately before the computer 1 is saved, and is composed of a system flag 62 and a power failure flag 63. There is. "1" (ON) of the system flag 62 indicates that the computer 1 immediately before
The state at the end of the processing of 1 is the state from the system startup to the transmission of the POFF (power OFF) command to the hardware, and indicates the abnormally terminated state in the operating state. System flag 62 "0" (OFF)
Indicates that the state when the processing of the computer 1 immediately before is completed is after the completion of the POFF (power OFF) command transmission to the hardware, and represents the normally completed state. "1" (energization) of the power failure flag 63 indicates that the processing is completed when the power supply is in the energized state. When the power failure flag 63 is "0" (power failure), it means that the power supply is interrupted and the processing is completed in the state where the power is supplied from UPS (uninterruptible power supply).

Next, according to the order shown in the flow chart of FIG. 5, the operation at the time of starting the computer 1 under the configuration of FIG. 1 will be described in detail. In FIG. 5, S21 is PON.
(Power ON) Instruct.

At S22, the system is started up. this is,
The system program is loaded, various initializations are performed, and the system (OS) of the computer 1 is started. S23
Reads the end flag 61 from the status file 6 and determines the content thereof.

In step S24, when the end flag 61 is "00" (system flag = 0, power failure flag = 0), the system is normally terminated and it is determined that the system is terminated due to a power failure. The raising is performed by the following S25 to S29.

In step S25, the user processing registration file (power recovery startup) is read. In S26, the user process 1 is activated. This starts the user process 1 by taking out the user process 1 from the head of the user process registration file 5 read in S25. At the time of this activation, the activation process is executed with the system account (privileges possessed by the system, all normal resources can be used).

In step S27, the execution UID of the process is changed. This takes out the execution UID (authority) corresponding to the process set in the user process registration file 5,
It is given to the started process and the usable resources are limited. As a result, the activated process independently executes the process using the resource under the authority of the execution UID.

In S28, after the lapse of t1 seconds, the process proceeds to the next step S29. This advances to S29 to activate the next process after the time t1 set in the user process registration file 5 has elapsed.

In step S29, it is determined whether it is the final process. YE
In the case of S, since the start of all processes has been completed,
Operation starts at S30. On the other hand, in the case of NO, since it is determined that all the processes have not been started, the process returns to S26 and is repeated, and the process of starting the next process registered in the user process registration file 5 and giving the execution UID are repeated. .

When the end flag is read at the time of starting the user process and it is determined to be the power recovery startup by the above S24 to S30, the user process registration file 5 for power recovery startup is read, and this user process is performed. Start from the first process of the registration file 5 sequentially, give the execution UID,
After the elapse of the set time, the next process is started and the execution UID is repeatedly given, so that all the processes can be automatically started sequentially.

In S31, when the end flag 61 is "01" (system flag = 0, power failure flag = 1), it is determined that the system has been normally completed and has been completed when the power is turned on. The raising is performed by the following S32 to S36.

In step S32, the user processing registration file (normal startup) is read. In S33, the user process 1 is activated. This starts the user process 1 from the beginning of the user process registration file 5 read in S32. At the time of this activation, the activation process is executed with the system account (privileges possessed by the system, all normal resources can be used).

In step S34, the execution UID of the process is changed. This takes out the execution UID (authority) corresponding to the process set in the user process registration file 5,
It is given to the started process and the usable resources are limited. As a result, the activated process independently executes the process using the resource under the authority of the execution UID.

In S35, after t1 seconds have elapsed, the process proceeds to S36 of the next step. This advances to S36 to activate the next process after the time t1 set in the user process registration file 5 has elapsed.

In step S36, it is determined whether it is the final process. YE
In the case of S, since the start of all processes has been completed,
Operation starts at S30. On the other hand, in the case of NO, since it is determined that all the processes have not been started, the process returns to S33 and is repeated, and the process of starting the next process registered in the user process registration file 5 and giving the execution UID are repeated. .

When the end flag is read at the time of starting the user process and it is determined that the user process is normally started by the above S31 to S36 and S30, the user process registration file 5 for normal start is read and this user process is executed. Start and execute U sequentially from the first process in the registration file 5
It is possible to sequentially automatically start all processes by assigning an ID, activating the next process after a lapse of a set time, and assigning an execution UID.

In S37, the end flag 61 is "10" (system flag = 1, power failure flag = 0) or "1".
In the case of 1 "(system flag = 1, power failure flag = 1), it is determined that the system has abnormally terminated (abnormal termination due to some cause during operation), so no execution (processing to start the user process) Is executed), a warning is given in S38 (a message indicating that the computer 1 has abnormally stopped during the previous operation of the system is displayed), and the operation of only the system is started in S30.

By the above S37, S38 and S30, when the end flag is read when the user process is started and the computer 1 is stopped while the system is operating, the process for starting the user process is executed. Instead, display a warning to that effect and start operating the system only.

Next, according to the order shown in the flowchart of FIG. 6, the operation for granting authority to the process started under the configuration of FIG. 1 will be described in detail. In FIG. 6, S
41 starts the process 1. This activates the user process 1 extracted from the user process registration file 5 in S5 or S12 of FIG.

In step S42, the execution UID is changed. This is changed to the execution UID of the user process on the shared memory 11 of FIG. 7, which will be described later. This is because when a process is started, the process creation means 2 uses the system's authority (usually has the authority to use all resources) to acquire an area, starts the process, and uses it after startup. The authority of this process is changed to the execution UID registered in the user process registration file 5.

In step S43, the process ID is acquired. This gets the ID of the started process. In S44, management information (process ID, time, etc.) is stored in the shared memory. This is because, as shown in FIG. 7, management information (process ID acquired in S43, process start time, execution UI) is stored in the area of the process provided in the shared memory 11.
(Such as D).

In S45, the process proceeds to S46 after the elapse of t1 seconds.
This was registered in the user processing registration file 5,
Since the "waiting time until the start of the next process" has elapsed, the process proceeds to S46 to start the next process.

In step S46, it is determined whether it is the final process. YE
In the case of S, since all the processes in the user process registration file 5 have been activated, the process ends (END). On the other hand, N
In the case of O, S41 and subsequent steps are repeated for the next process.

By the above, the user processing registration file 5
Process names are sequentially fetched from and started up and executed
By repeatedly storing the ID, the process ID, and the activation time as management information in the shared memory 11, it becomes possible to give authority to the process and activate it.

FIG. 7 is a diagram for explaining the management of the process of the present invention. This management information is stored in the shared memory 11 and is information for the entire process started by the user processing registration file 5.-User registration processing operating state-000 No operation-001 Normal Startup ・ 010 Power recovery startup ・ 011 Normal termination ・ 100 Power failure termination ・ Number of registered user processes n ・ Registering the user process number i that is being executed and for each process ・ i-th user process ID ・i-th user process execution UID (authority) -i-th user process startup time-i-th next process startup wait time ti is registered.

[0054]

As described above, according to the present invention,
The user process registration file 5 was provided, and the processes set in the user process registration file 5 were automatically started and set at the set time intervals in the set order when the computer 1 was started up or finished. Since the configuration that grants the authority is adopted, it is possible to automate the start-up process and the end process of the user process of the computer 1, and the user process that is started at the time of start-up or end depending on the application. , Order, time interval, and authority can be changed easily.

[Brief description of drawings]

FIG. 1 is a principle block diagram of the present invention.

FIG. 2 is a flowchart for explaining the overall operation of the present invention.

FIG. 3 is an example of a user process registration file of the present invention.

FIG. 4 is an example of a status file of the present invention.

FIG. 5 is a flowchart for explaining the operation of the present invention at startup.

FIG. 6 is an authorization flow chart of the present invention.

FIG. 7 is a management explanatory diagram of a process of the present invention.

[Explanation of symbols]

 1: Computer 2: Process creating means 3: Control table 4: User process 5: User processing registration file 6: Status file 61: End flag 62: System flag 63: Power failure flag 7: Power control device 11: Shared memory

Claims (2)

[Claims] 1. A user process registration file (5) for registering a plurality of process names and times in advance, and a set time elapses after a process having the process name of the user process registration file (5) is started. An automatic start-up device comprising: a process creating means (2) that repeats starting a process with the next process name later. 2. A user process registration file (5) in which a process name and authority are registered in advance, and the process authority of the process name of the user process registration file (5) is defined as the registered authority. An automatic start-up device comprising a process creating means (2) for executing the process.