CN112199237A - System service recovery method and device and electronic equipment - Google Patents
System service recovery method and device and electronic equipment Download PDFInfo
- Publication number
- CN112199237A CN112199237A CN202011105413.8A CN202011105413A CN112199237A CN 112199237 A CN112199237 A CN 112199237A CN 202011105413 A CN202011105413 A CN 202011105413A CN 112199237 A CN112199237 A CN 112199237A
- Authority
- CN
- China
- Prior art keywords
- file
- target
- subfile
- running
- application program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Retry When Errors Occur (AREA)
Abstract
The application discloses a system service recovery method, a device and electronic equipment, belonging to the technical field of electronic equipment, wherein the method is applied to the electronic equipment, and the electronic equipment comprises the following steps: in the case of system crash, killing the target file in the target folder; receiving a system restoring instruction, and restoring the first file; running the first file and the second file to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file. According to the system service recovery method, the target file in the target folder can be killed only in a targeted mode, then the second file replacing the target file is operated, the system service can be recovered, a complex and time-consuming starting process is not required to be executed, and the time consumed for recovering the system service is short.
Description
Technical Field
The embodiment of the application relates to the technical field of electronic equipment, in particular to a system service recovery method and device and electronic equipment.
Background
In the era of mobile internet, along with the popularization of intelligent electronic devices, electronic devices gradually become portable equipment for people to live, work and travel. The operating system of the present electronic device mainly includes: android system and iOS system. The Android system is now used as a main operating system of the electronic device, and is open-source, and manufacturers can customize or even deeply modify the Android system, so that the stability of the modified system can directly affect the user experience.
At present, when an Android system crashes in the operation process, all application processes are killed, the parent processes and other core service processes of the application processes are restarted, namely, a starting process is executed once, the system service can be restored only by entering a starting main interface after the Android system is restarted, and the system service restoration consumes a long time.
Disclosure of Invention
The embodiment of the application aims to provide a system service recovery method, which can solve the problem that the system service recovery in the prior art takes long time.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present application provides a method for recovering a system service, where the method includes: in the case of system crash, killing the target file in the target folder; receiving a system restoring instruction, and restoring the first file; running the first file and the second file to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file.
In a second aspect, an embodiment of the present application provides a system service recovery apparatus, where the system service recovery apparatus includes: the killing module is used for killing the target file in the target folder under the condition that the system crashes; the receiving module is used for receiving a system restoring instruction and restoring the first file; the first operation module is used for operating the first file and the second file so as to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file.
In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect.
In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.
In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.
In the embodiment of the application, the target file in the target folder is killed under the condition that the system is crashed; receiving a system restoring instruction, and restoring the first file; the first file and the second file are operated to recover the system service, the target file can be killed in a targeted mode, then the second file replacing the target file is operated to recover the system service, a complex and time-consuming starting process is not required to be executed, and the time consumed for recovering the system service is short.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a flow chart illustrating the steps of a system service recovery method according to an embodiment of the present application;
fig. 2 is a schematic flowchart illustrating a service recovery method for an Android system according to an embodiment of the present application;
fig. 3 is a block diagram showing a system service recovery apparatus according to an embodiment of the present application;
fig. 4 is a block diagram showing a configuration of an electronic device according to an embodiment of the present application;
fig. 5 is a schematic diagram illustrating a hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
The system service recovery provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.
Referring to fig. 1, a flowchart illustrating steps of a system service recovery method according to an embodiment of the present application is shown.
The system service recovery method of the embodiment of the application comprises the following steps:
step 101: in the event of a system crash, the target file in the target folder is killed.
The target folder contains the relevant process files of system startup, such as: parent processes of application processes, system service processes, backup system service processes, and other core service processes.
Step 102: and receiving a system restoring instruction and restoring the first file.
And when the system service is down, determining that a system recovery instruction is received after the parent process of the application process receives the death signal.
The first file is a file except the third file in the target file, and the content of the third file is a system service process.
Step 103: and running the first file and the second file to recover the system service.
And the second file is stored in the target folder, the content of the second file is the same as that of a third file in the target file, and the content of the second file is a backup system service process.
After receiving the system recovery instruction, the parent process of the application process is not restarted, and the backup system service process is directly used for replacing the system service process in the killed target file, so that the system recovery speed can be accelerated.
According to the system service recovery method provided by the embodiment of the application, the target file in the target folder is killed under the condition that the system is crashed; receiving a system restoring instruction, and restoring the first file; the first file and the second file are operated to recover the system service, the target file can be killed in a targeted mode, then the second file replacing the target file is operated to recover the system service, a complex and time-consuming starting process is not required to be executed, and the time consumed for recovering the system service is short.
In an optional embodiment, before the step of killing the target file in the target folder in case of a system crash, the method further comprises the steps of:
the method comprises the following steps: under the condition of receiving a starting-up instruction, operating the first file and the third file;
step two: when the first subfile contained in the third file is initialized, the results of the installation package and the repository object scanned during the running of the first subfile are stored in the system directory.
The first subfile contains the PMS, which is an abbreviation of PackageManagerService, and the PMS is one of the core services in the system, and manages all the tasks related to the software package, such as: and installing and uninstalling the application software package.
The scanned installation package and resource library object results are locally serialized to a system directory for storage when the PMS manages the service, so that the PMS which backs up the service process of the system when the system is down is started more quickly, and the time consumption of rescanning the resource package when the PMS service is initialized can be saved.
In an optional embodiment, the specific way of running the first file and the second file is as follows:
in the process of operating the first file and the second file, when a second subfile contained in the second file is initialized, obtaining a result of an installation package and a resource library object stored in a system directory as a scanning result of the second subfile;
wherein the first subfile and the second subfile have the same content.
In the alternative embodiment, the scanning result is directly obtained from the system target without scanning the installation package and the resource library object, and the time consumption is short.
In an optional embodiment, before the step of killing the target file in the target folder in case of a system crash, the method further comprises the steps of:
first, the third subfile is run.
And the third subfile is used for recording the identification information of the running application program. The third subfile contains components for managing and scheduling the application process, such as the AMS in the android system.
And secondly, correspondingly storing the starting time of the application program and the identification information of the application program to a preset storage space.
The identification information of the application program running in the running process of the system is recorded through the third subfile, so that the running of the application program can be recovered quickly after the system is restarted.
In an optional embodiment, after the step of running the first file and the second file to restore the system service, the method further comprises the steps of:
acquiring target identification information with the shortest starting time and system collapse time from a preset storage space;
determining a target application program corresponding to the target identification information as an application program which is running when the system crashes;
the target application is launched.
According to the optional mode, the application program which is operated in the foreground before the system service is down can be directly started after the system service is recovered, a user does not need to manually start the target application program, and the operation is convenient and fast.
Referring to fig. 2, a system service recovery method provided in the embodiment of the present application is described with reference to a specific application scenario of an Android system, where the system service recovery method in the specific example may be divided into four pieces of content, which are as follows:
a first part: after the system is started, Zygote is created, and then the Zygote creates a system server process and a Second system server process.
Specifically, zygate creates a Systemserver process, then creates a Second Systemserver process, the name of the Second Systemserver process may be set to Systemserver _ hellp, and the Second Systemserver process is set to start after waiting for the downtime signal sent by zygate.
A second part: the result of the scanned object is locally serialized when the PMS service in the Systemserver service is initialized.
Specifically, the results of scanning the installation package and the resource library object are locally serialized into a system directory for storage when the PMS manages the service, and when the PMS of the Second system server is started when the system is down, the time consumption of rescanning the installation package and the resource library object when the PMS service is initialized can be saved.
And a third part: after system service is down, Zygote receives death signal child. At this time, Zygote process suicide processing optimization is to set a downtime attribute to an attribute service, notify the Init to kill all application processes created by Zygote except a Second system server process, send the attribute notification to the Init to enable the Init to call a reset interface of a Native system service or restart the Native Services process, then wait for the running attributes of all core Services to become running and then send a wake-up signal to the backed-up Second system server process, the backed-up Second system server process returns from blocking after receiving the signal, modifies the process name to be a system server, executes a code formal replacement system server process which is the same as the system server process, and then determines whether to scan an installation package or a resource library object according to the attributes of the server when the PMS is initialized. And if the system is down and the scanning variables are reconstructed directly from the local serialization files, all the services are initialized and the main interface is started.
The fourth part: after the system service is quickly recovered to be started, the system service can be continuously used.
Specifically, after the system is started, the downtime attribute is cleared, and all components are restored as the initial state.
The method for recovering the system service provided in this embodiment can recover the system service more quickly even if a system problem occurs. In the method, on one hand, a Zygote preloading flow does not need to be repeated when the system service is restored; on the other hand, Zygote creates a Second Systemserver process at the same time of creating the Systemserver process so as to replace the crashed Systemserver process at any time; in another aspect, the startup optimization is also implemented on the recovered systeserer PMS, and the time consumed by system service recovery can be effectively shortened by combining the three aspects.
It should be noted that, in the system service recovery method provided in the embodiment of the present application, the execution subject may be a system service recovery device, or a control module in the system service recovery device for executing the system service recovery method. In the embodiment of the present application, a system service recovery module is taken as an example to execute a system service recovery method, and a system service recovery device provided in the embodiment of the present application is described.
Fig. 3 is a block diagram of a system service recovery apparatus for implementing an embodiment of the present application.
The system service recovery apparatus 300 according to the embodiment of the present application includes:
a killing module 301, configured to kill a target file in a target folder in the case of a system crash;
a receiving module 302, configured to receive a system recovery instruction and recover the first file;
a first operation module 303, configured to operate the first file and the second file to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file.
Optionally, the apparatus further comprises:
the second operation module is used for operating the first file and the third file under the condition of receiving a starting instruction before the killing module kills the target file in the target folder under the condition of system breakdown;
and the first storage module is used for storing the results of the installation package and the resource library object scanned during the running of the first subfile into the system directory when the first subfile contained in the third file is initialized.
Optionally, the first module is specifically configured to:
in the process of running the first file and the second file, when a second subfile contained in the second file is initialized, obtaining the result of the installation package and the resource library object stored in the system directory as the scanning result of the second subfile;
wherein the first subfile is identical in content to the second subfile.
Optionally, the apparatus further comprises: the third operation module is used for operating a third subfile, wherein the third subfile is used for recording the identification information of the operating application program;
and the second storage module is used for correspondingly storing the starting time of the application program and the identification information of the application program to a preset storage space.
Optionally, the apparatus further comprises: the searching module is used for acquiring the target identification information with the shortest starting time and the shortest system crash time from the preset storage space after the first running module runs the first file and the second file so as to complete system restart; determining a target application program corresponding to the target identification information as an application program which is running when the system crashes; and the starting module is used for starting the target application program.
The system service recovery device provided by the embodiment of the application kills the target file in the target folder under the condition of system crash; receiving a system restoring instruction, and restoring the first file; the first file and the second file are operated to recover the system service, the target file can be killed in a targeted mode, then the second file replacing the target file is operated to recover the system service, a complex and time-consuming starting process is not required to be executed, and the time consumed for recovering the system service is short.
The system service recovery device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiments of the present application are not particularly limited.
The distance measuring device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system (Android), an iOS operating system, or other possible operating systems, which is not specifically limited in the embodiments of the present application.
The system service recovery apparatus provided in the embodiment of the present application can implement each process implemented in the method embodiments of fig. 1 to fig. 2, and is not described here again to avoid repetition.
Optionally, as shown in fig. 4, an electronic device 400 is further provided in this embodiment of the present application, and includes a processor 401, a memory 402, and a program or an instruction stored in the memory 402 and executable on the processor 401, where the program or the instruction is executed by the processor 401 to implement each process of the foregoing embodiment of the system service recovery method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and the non-mobile electronic devices described above.
Fig. 5 is a schematic diagram of a hardware structure of an electronic device implementing an embodiment of the present application.
The electronic device 500 includes, but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 707, an interface unit 508, a memory 509, a processor 510, and the like.
Those skilled in the art will appreciate that the electronic device 500 may further include a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 510 via a power management system, so as to implement functions of managing charging, discharging, and power consumption via the power management system. The electronic device structure shown in fig. 5 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.
The processor 510 is configured to kill the target file in the target folder in the case of a system crash; receiving a system restoring instruction, and restoring the first file; running the first file and the second file to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file.
In the embodiment of the application, the electronic equipment kills the target file in the target folder under the condition of system crash; receiving a system restoring instruction, and restoring the first file; the first file and the second file are operated to recover the system service, the target file can be killed in a targeted mode, then the second file replacing the target file is operated to recover the system service, a complex and time-consuming starting process is not required to be executed, and the time consumed for recovering the system service is short.
Optionally, the processor 510 is further configured to, in the case of a system crash, execute the first file and the third file in the case of receiving a boot instruction before killing the target file in the target folder; and when a first subfile contained in the third file is initialized, storing the result of the installation package and the resource library object scanned during the running of the first subfile into a system directory.
Optionally, when the processor 510 runs the first file and the second file, it is specifically configured to: in the process of running the first file and the second file, when a second subfile contained in the second file is initialized, obtaining the result of the installation package and the resource library object stored in the system directory as the scanning result of the second subfile; wherein the first subfile is identical in content to the second subfile.
Optionally, the processor 510 is further configured to, before killing the target file in the target folder in case of a system crash: running a third subfile, wherein the third subfile is used for recording identification information of the running application program; and correspondingly storing the starting time of the application program and the identification information of the application program to a preset storage space.
Optionally, the processor 510 is further configured to, after the first file and the second file are run to recover the system service, obtain target identification information with a shortest starting time and a shortest system crash time from the preset storage space; determining a target application program corresponding to the target identification information as an application program which is running when the system crashes; and starting the target application program.
It should be understood that in the embodiment of the present application, the input Unit 504 may include a Graphics Processing Unit (GPU) 5041 and a microphone 5042, and the Graphics processor 5041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 507 includes a touch panel 5071 and other input devices 5072. A touch panel 5071, also referred to as a touch screen. The touch panel 5071 may include two parts of a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in further detail herein. The memory 509 may be used to store software programs as well as various data including, but not limited to, application programs and operating systems. Processor 510 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing system service recovery method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the system service recovery method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the description is omitted here.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (11)
1. A method for system service recovery, the method comprising:
in the case of system crash, killing the target file in the target folder;
receiving a system restoring instruction, and restoring the first file;
running the first file and the second file to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file.
2. The method of claim 1, wherein prior to the step of killing the target file in the target folder in the event of a system crash, the method further comprises:
under the condition of receiving a starting-up instruction, operating the first file and the third file;
and when a first subfile contained in the third file is initialized, storing the result of the installation package and the resource library object scanned during the running of the first subfile into a system directory.
3. The method of claim 2, wherein the step of running the first file and the second file comprises:
in the process of running the first file and the second file, when a second subfile contained in the second file is initialized, obtaining the result of the installation package and the resource library object stored in the system directory as the scanning result of the second subfile;
wherein the first subfile is identical in content to the second subfile.
4. The method of claim 1, wherein prior to the step of killing the target file in the target folder in the event of a system crash, the method further comprises:
running a third subfile, wherein the third subfile is used for recording identification information of the running application program;
and correspondingly storing the starting time of the application program and the identification information of the application program to a preset storage space.
5. The method of claim 4, wherein after the step of running the first file and the second file to restore system services, the method comprises:
acquiring target identification information with the shortest starting time and system collapse time from the preset storage space;
determining a target application program corresponding to the target identification information as an application program which is running when the system crashes;
and starting the target application program.
6. A system service recovery apparatus, the apparatus comprising:
the killing module is used for killing the target file in the target folder under the condition that the system crashes;
the receiving module is used for receiving a system restoring instruction and restoring the first file;
the first operation module is used for operating the first file and the second file so as to recover the system service; the second file is stored in a target folder, the content of the second file is the same as that of a third file in the target file, and the first file is a file in the target file except the third file.
7. The apparatus of claim 6, further comprising:
the second operation module is used for operating the first file and the third file under the condition of receiving a starting instruction before the killing module kills the target file in the target folder under the condition of system breakdown;
and the first storage module is used for storing the results of the installation package and the resource library object scanned during the running of the first subfile into the system directory when the first subfile contained in the third file is initialized.
8. The apparatus of claim 7, wherein the first module is specifically configured to:
in the process of running the first file and the second file, when a second subfile contained in the second file is initialized, obtaining the result of the installation package and the resource library object stored in the system directory as the scanning result of the second subfile;
wherein the first subfile is identical in content to the second subfile.
9. The apparatus of claim 6, further comprising:
the third operation module is used for operating a third subfile, wherein the third subfile is used for recording the identification information of the operating application program;
and the second storage module is used for correspondingly storing the starting time of the application program and the identification information of the application program to a preset storage space.
10. The apparatus of claim 9, further comprising:
the searching module is used for acquiring the target identification information with the shortest starting time and the shortest system crash time from the preset storage space after the first running module runs the first file and the second file so as to complete system restart;
determining a target application program corresponding to the target identification information as an application program which is running when the system crashes;
and the starting module is used for starting the target application program.
11. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the system service recovery method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011105413.8A CN112199237B (en) | 2020-10-15 | 2020-10-15 | System service recovery method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011105413.8A CN112199237B (en) | 2020-10-15 | 2020-10-15 | System service recovery method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112199237A true CN112199237A (en) | 2021-01-08 |
| CN112199237B CN112199237B (en) | 2023-05-26 |
Family
ID=74009795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011105413.8A Active CN112199237B (en) | 2020-10-15 | 2020-10-15 | System service recovery method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199237B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1484152A (en) * | 2002-09-18 | 2004-03-24 | 宏基股份有限公司 | Method and device for restoring computer operation system and method for producing said system |
| CN103049343A (en) * | 2011-10-14 | 2013-04-17 | 腾讯科技（深圳）有限公司 | Method and device for restoring operating system blue screen |
| CN105468478A (en) * | 2015-11-26 | 2016-04-06 | 北京京东尚科信息技术有限公司 | Recovery method and apparatus for business data after application crash |
-
2020
- 2020-10-15 CN CN202011105413.8A patent/CN112199237B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1484152A (en) * | 2002-09-18 | 2004-03-24 | 宏基股份有限公司 | Method and device for restoring computer operation system and method for producing said system |
| CN103049343A (en) * | 2011-10-14 | 2013-04-17 | 腾讯科技（深圳）有限公司 | Method and device for restoring operating system blue screen |
| CN105468478A (en) * | 2015-11-26 | 2016-04-06 | 北京京东尚科信息技术有限公司 | Recovery method and apparatus for business data after application crash |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112199237B (en) | 2023-05-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112486444B (en) | Screen projection method, device, equipment and readable storage medium | |
| CN112099684A (en) | Search display method and device and electronic equipment | |
| CN111813305A (en) | Application program starting method and device | |
| CN105867962A (en) | System upgrading method and device | |
| CN112417420A (en) | Information processing method and device and electronic equipment | |
| CN113992615B (en) | Method and device for displaying withdrawal message, electronic equipment and storage medium | |
| US20240184434A1 (en) | Display method and apparatus | |
| CN113138786B (en) | Application updating method and device | |
| CN112905209B (en) | Application program updating method and device | |
| CN107861827B (en) | Card screen detection method, mobile terminal and computer readable storage medium | |
| CN112558833B (en) | Application running method and device and electronic equipment | |
| CN113138785A (en) | Application program updating method and device | |
| CN113282435B (en) | Application exception processing method and electronic equipment | |
| CN112199237B (en) | System service recovery method and device and electronic equipment | |
| CN113127425B (en) | Picture processing method and device and electronic equipment | |
| CN107608827B (en) | Backup method and terminal for package configuration file and related medium product | |
| CN113962316A (en) | Model training method and device and electronic equipment | |
| CN111766992B (en) | Information display method and device, electronic equipment and storage medium | |
| CN113868269A (en) | Screenshot method and device, electronic equipment and readable storage medium | |
| CN113282830A (en) | Display method and display device | |
| CN113037871A (en) | Conference call recovery method, device, system, electronic equipment and readable storage medium | |
| CN112291584A (en) | Dynamic effect file processing method and device and electronic equipment | |
| CN111880912A (en) | Method and device for controlling electronic equipment and electronic equipment | |
| CN114398129B (en) | Sharing method and device for sharing objects, electronic equipment and readable storage medium | |
| CN113220325B (en) | Program processing method, apparatus, electronic device, and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |