WO2021057855A1 - 程序进程监控的方法、装置、计算机设备及可读存储介质 - Google Patents

程序进程监控的方法、装置、计算机设备及可读存储介质 Download PDF

Info

Publication number
WO2021057855A1
WO2021057855A1 PCT/CN2020/117490 CN2020117490W WO2021057855A1 WO 2021057855 A1 WO2021057855 A1 WO 2021057855A1 CN 2020117490 W CN2020117490 W CN 2020117490W WO 2021057855 A1 WO2021057855 A1 WO 2021057855A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
monitored process
monitored
log
name
Prior art date
Application number
PCT/CN2020/117490
Other languages
English (en)
French (fr)
Inventor
蒋旭晨
王剑侠
沈杰
林晓君
Original Assignee
三维通信股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 三维通信股份有限公司 filed Critical 三维通信股份有限公司
Publication of WO2021057855A1 publication Critical patent/WO2021057855A1/zh

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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079—Root cause analysis, i.e. error or fault diagnosis
    • 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/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device, computer equipment, and readable storage medium for program process monitoring.
  • a process is a running activity of a program on a certain data set in a computer. It is the basic unit of the system for resource allocation and scheduling, and is the foundation of the operating system structure.
  • application programs are processes stored in the operating system.
  • some monitoring and management methods need to be added.
  • how to effectively and timely monitor the process of application programs in the operating system So as to prevent the abnormal exit of the application program and prevent the application program from entering an endless loop, it needs to be solved urgently.
  • a method for program progress monitoring includes:
  • the monitored process According to the name and parameter information of the monitored process, start the monitored process, and create a log file to save the log information output by the monitored process according to the name and current time of the monitored process;
  • the method includes:
  • the modification status is that the first file is modified normally, re-check the first file in the configuration file, and back up the re-verified first file to the backup partition;
  • the modification status is that the first file is abnormally modified
  • the first file is overwritten with the first backup file of the backup partition.
  • the recovery operation of the application or device of the monitored process according to the log file includes:
  • the verification of the first file in the configuration file corresponding to the monitored process according to the name of the monitored process includes:
  • a message digest algorithm 5 (Message-Digest Algorithm, referred to as MD5) verification check is performed on the first file in the configuration file corresponding to the monitored process.
  • the initiating the monitored process includes:
  • a device for program progress monitoring includes:
  • the verification module is used to read the configuration file monitored by the program, obtain the name and parameter information of the monitored process, and compare the first in the configuration file corresponding to the monitored process according to the name of the monitored process. The file is checked to determine whether the first file has been illegally modified;
  • a data backup and recovery module configured to overwrite the first file with the first backup file of the backup partition when it is determined that the first file is illegally modified
  • the creation module is configured to start the monitored process according to the name and parameter information of the monitored process, and create a log file to save the log information output by the monitored process according to the name and current time of the monitored process;
  • the recovery module is used to obtain the log file of the exit of the monitored process, and perform a recovery operation on the application or device of the monitored process according to the log file of the exit of the monitored process, wherein the error of the monitored process Or abnormal information causes the monitored process to exit.
  • the device further includes:
  • the data backup module is used to monitor the modification status of the first file in the configuration file corresponding to the monitored process after the creation of the log file saves the log information output by the monitored process, and in the modification status When the first file is modified normally, the first file in the configuration file is re-checked, and the re-verified first file is backed up to the backup partition; in the modification status When the first file is modified abnormally, the first file is overwritten with the first backup file of the backup partition.
  • the recovery module includes:
  • the shutdown restart unit is configured to shut down the application program corresponding to the monitored process, and restart the device corresponding to the monitored process according to the log file.
  • a computer device including a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • the processor implements the above program when the computer program is executed. The steps of the process monitoring method.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned program process monitoring method are realized.
  • Fig. 1 is a schematic diagram of an application environment of a method for program progress monitoring according to an embodiment of the present application.
  • Fig. 2 is a flowchart of a method for program progress monitoring according to an embodiment of the present application.
  • Fig. 3 is a first structural block diagram of a device for monitoring program progress according to an embodiment of the present application.
  • Fig. 4 is a second structural block diagram of a device for program progress monitoring according to an embodiment of the present application.
  • Fig. 5 is a third structural block diagram of a device for program progress monitoring according to an embodiment of the present application.
  • Fig. 6 is a flowchart of a method for monitoring program progress based on an embedded Linux system according to an embodiment of the present application.
  • first and second are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with “first” and “second” may explicitly or implicitly include at least one of the features.
  • a plurality of means at least two, such as two, three, etc., unless specifically defined otherwise.
  • everal means at least one, such as one, two, etc., unless otherwise specifically defined.
  • FIG. 1 is a schematic diagram of an application environment of a method for program process monitoring in an embodiment of the present application. As shown in FIG. 1, it can be applied to the method for program process monitoring.
  • the terminal 101 communicates with the server 102 through the network.
  • the terminal 101 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
  • the server 102 can be embedded It can be realized by a device server, an independent server, or a server cluster composed of multiple servers.
  • the operating systems installed on the terminal 101 and the server 102 include: embedded Linux system, Unix system, Windows system, Android system and Ios system, etc.
  • the operating systems of the terminal 101 and server 102 can read the configuration file of the monitoring program, according to the receiving The name of the monitoring process, the first file in the configuration file corresponding to the monitored process is checked, and if the first file is determined to be illegally modified, the first backup file of the backup partition is used to overwrite the first file.
  • a file; according to the name of the monitored process and the current time, create a log file to save the log information output by the monitored process; restore the application or device of the monitored process according to the log file, and solve the problem of the application The question of how to effectively and timely monitor the processes in the operating system ensures the stable and orderly operation of the application program.
  • FIG. 2 is a flowchart of a method for monitoring program progress according to an embodiment of the present application. As shown in FIG. 2, the method includes the following steps:
  • Step S201 Read the configuration file monitored by the program, obtain the name and parameter information of the monitored process, and verify the first file in the configuration file corresponding to the monitored process according to the name of the monitored process. Determine whether the first file has been illegally modified;
  • Step S202 In the case where it is determined that the first file is illegally modified, overwrite the first file with the first backup file of the backup partition;
  • the embedded device causes important file damage or artificially modify the file illegally in the case of a sudden power failure, the first file can be illegally modified;
  • Step S203 Start the monitored process according to the name and parameter information of the monitored process, and create a log file to save the log information output by the monitored process according to the name and current time of the monitored process;
  • Step S204 Obtain the log file of the monitored process exit, and perform a recovery operation on the application or device of the monitored process according to the log file of the monitored process exit, wherein the error or abnormal information of the monitored process causes The monitored process exits.
  • the monitored process is verified according to the configuration file, and the startup of the monitored process is determined.
  • the log information of the monitored process is saved by creating a log file.
  • the monitored application or device is restored through the log file, which solves the problem of how to effectively monitor the process of the application in the operating system in a timely manner, and ensures the stable and orderly operation of the application.
  • the monitoring program has checked the configuration file before starting the monitored process.
  • the first file has been overwritten with the first backup file.
  • no illegal modification after starting the monitored process, it is necessary to monitor whether the first file in the monitored process has been modified in real time. After receiving the modification command or modification notification, the first file has been modified normally.
  • the monitoring program re-checks the first file in the configuration file, and backs up the re-verified first file to the backup partition.
  • the monitoring program before starting the monitored process, the monitoring program The configuration file has been verified. In the case of illegal modification, the first file has been overwritten with the first backup file.
  • the first backup file in the monitored process After starting the monitored process, it is necessary to monitor in real time whether the first backup file in the monitored process has been Modification: After not receiving a modification command or modification notice, it is determined that the first backup file has been illegally modified, and the first backup file in the backup partition is used to overwrite the illegally modified first backup file. Before the monitoring process runs and during the monitoring process, it monitors whether the configuration file is modified, and monitors whether the configuration file of the application program has been illegally tampered with in real time.
  • the way of restoring the application or device of the monitored process will be different, for example, the monitored process exits
  • the reason is only related to the application.
  • the recovery operation only needs to restart the application according to the log file records to solve the program failure.
  • the reason for the exit of the monitored process may be caused by the hardware information of the device, for example, the memory Cache error conditions, or it is impossible to determine whether it is an application problem or a device hardware problem, or an application or device is in an infinite loop.
  • the record of the above log file can also be provided to maintenance personnel.
  • the above implementation method can automatically start the application or device when the monitored process exits during the monitoring process, ensuring that The stability of the application program, in addition, through the analysis of the exit reason of the monitored process recorded in the log file, it provides a reference for subsequent application program modification.
  • the first file in the configuration file corresponding to the monitored process can be verified according to the name of the monitored process in multiple ways, for example, according to the monitored process Name, the information digest algorithm 5 (MD5) check is performed on the first file in the configuration file corresponding to the monitored process, and the MD5 operation is performed on the first file of the configuration file, and the calculated result is the same as the pre-stored first file.
  • the check codes of the files are compared. If they are the same, the first file has not been modified. Otherwise, it is considered that the first file has been modified and the first file needs to be overwritten with the first backup file.
  • the verification method can also include information digest algorithm 2 (Message-Digest Algorithm 2, abbreviated as MD2) and Message-Digest Algorithm 4 (Message-Digest Algorithm 4, abbreviated as MD4), etc.
  • MD2 Message-Digest Algorithm 2, abbreviated as MD2
  • MD4 Message-Digest Algorithm 4, abbreviated as MD4
  • the way to start the monitored process can be to start the monitored process by means of pipes, and can also use named pipes (First Input First Output, FIFO for short) and signal pipes ( Signal) and other methods to start the monitored process.
  • pipes First Input First Output, FIFO for short
  • signal pipes Signal
  • a device for monitoring program progress is also provided, which is used to implement the above-mentioned embodiments and preferred implementations, and what has been described will not be repeated.
  • the term "module” can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • FIG. 3 is a structural block diagram 1 of a device for monitoring program progress according to an embodiment of the present application. As shown in FIG. 3, the device includes:
  • the verification module 31 is used to read the configuration file monitored by the program, obtain the name and parameter information of the monitored process, and perform processing on the first file in the configuration file corresponding to the monitored process according to the name of the monitored process Check to determine whether the first file has been illegally modified;
  • the data backup and recovery module 32 is configured to overwrite the first file with the first backup file of the backup partition when it is determined that the first file is illegally modified;
  • the creation module 33 is used to start the monitored process according to the name and parameter information of the monitored process, and create a log file to save the log information output by the monitored process according to the name and current time of the monitored process;
  • the recovery module 34 is used to obtain the log file of the exit of the monitored process, and perform a recovery operation on the application or device of the monitored process according to the log file of the exit of the monitored process.
  • the abnormal information caused the monitored process to exit.
  • the verification module 31 and the data backup and recovery module 32 verify the monitored process according to the configuration file, and the creation module 33 determines the startup of the monitored process. After startup, it saves the monitored process by creating a log file. Log information.
  • the recovery module 34 restores the monitored application or device through the log file, which solves how to effectively monitor the process of the application in the operating system in a timely manner The problem, to ensure the stable and orderly operation of the application.
  • FIG. 4 is a second structural block diagram of a device for monitoring program progress according to an embodiment of the present application. As shown in FIG. 4, the device includes:
  • the data backup module 42 is configured to monitor the modification status of the first file in the configuration file corresponding to the monitored process after the creation of the log file and save the log information output by the monitored process, where the modification status is the first When the file is modified normally, re-check the first file in the configuration file, and back up the re-verified first file to the backup partition; in the modification status, the first file is not In the case of normal modification, the first file is overwritten with the first backup file of the backup partition, and the first backup file is copied to the configuration file partition to ensure that the monitored program obtains the correct configuration information.
  • FIG. 5 is a structural block diagram 3 of a device for monitoring program progress according to an embodiment of the present application. As shown in FIG. 5, the device includes:
  • the recovery module 38 includes a shutdown and restart unit 52 configured to shut down the application program corresponding to the monitored process, and restart the device corresponding to the monitored process according to the log file.
  • the method of monitoring the program process based on the embedded Linux system includes: process monitoring, configuration file modification monitoring, backup and device restart, etc.
  • Figure 6 is based on the embodiment of the present application Based on the flow chart of the method for monitoring the program process based on the embedded Linux system, as shown in Figure 6, the method steps include:
  • Step S601 Read the configuration file of the monitoring program, and obtain the name of the process to be monitored and related parameters;
  • Step S602 After obtaining the name of the monitored process, MD5 check is performed on the related files of the configuration folder of the corresponding process to determine whether the file has been illegally modified;
  • Step S603 If there are files in the configuration folder of the monitored process that are illegally modified, which may cause the process to fail to start normally, the latest backup from the backup partition will overwrite the current related files;
  • Step S604 According to the acquisition of the required monitored process name and related parameters, start the corresponding monitored process through the pipe method;
  • Step S605 According to the requirement of whether the monitored process outputs log information (log file information), create a log file with the current system time and process name in the corresponding log folder to save the output log information of the monitored process;
  • Step S606 Whether the configuration file corresponding to the monitored process is modified by the monitoring program in real time. If the file is modified, the file needs to be re-verified and the new file is backed up to the backup partition;
  • Step S607 During the running process of the monitored process, an error or abnormality of one or several processes causes the process to exit, the system will send an exit message to the monitoring program, so that the monitoring program records the status of the relevant process to the local log file and closes After the relevant application, restart the device.
  • the monitoring program of the Linux system completes the functions of program process monitoring, configuration file modification monitoring backup and device restart, which solves the problem of how to effectively and timely monitor the process of the application in the Linux system, and ensures the application Stable and orderly operation.
  • a software is also provided, and the software is used to execute the technical solutions described in the above-mentioned embodiments and preferred embodiments.
  • a storage medium stores the above-mentioned software.
  • the storage medium includes, but is not limited to, an optical disk, a floppy disk, a hard disk, and a rewritable memory.
  • Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种程序进程监控的方法、装置、计算机设备及可读存储介质，其中，该方法包括：读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据该受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行校验核对，判断该第一文件是否被非法修改（S201）；在确定所述第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖所述第一文件（S202）；根据该受监控进程的名称和参数信息，启动该受监控进程，依据该受监控进程的名称和当前时间，创建日志文件保存该受监控进程输出的日志信息（S203）；获取该受监控进程退出的日志文件，依据该受监控进程退出的日志文件对该受监控进程的应用程序或者设备进行恢复操作，其中，该受监控进程的错误或异常信息引起该受监控进程退出（S204）。该方法解决了应用程序在操作系统中的进程如何有效及时监控的问题，保证了应用程序的稳定有序的运行。

Description

[根据细则26改正13.10.2020]　程序进程监控的方法、装置、计算机设备及可读存储介质
相关申请
[根据细则26改正13.10.2020]　
本申请要求2019年9月26日申请的，申请号为201910918237.0，发明名称为“程序进程监控的方法、装置、计算机设备及可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别是涉及一种程序进程监控的方法、装置、计算机设备及可读存储介质。
背景技术
进程是计算机中的程序关于某数据集合上的一次运行活动，是系统进行资源分配和调度的基本单位，是操作系统结构的基础。
一般应用程序都是进程存在操作系统中，为了保证应用程序稳定、有序地运行，都会需要增加监控和管理的一些手段，在相关技术中，如何有效及时地监控应用程序在操作系统中的进程，从而来防止应用程序的异常退出，以及防止应用程序进入死循环的问题，目前需要亟待解决。
针对相关技术中，应用程序在操作系统中的进程如何有效及时监控的问题，目前尚未提出有效的解决方案。
发明内容
根据本申请的各种实施例，提供一种程序进程监控的方法，所述方法包括：
读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行校验核对，判断所述第一文件是否被非法修改；
在确定所述第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖所述第一文件；
根据所述受监控进程的名称和参数信息，启动所述受监控进程，依据所述受监控进程的名称和当前时间，创建日志文件保存所述受监控进程输出的日志信息；
获取所述受监控进程退出的日志文件，依据所述受监控进程退出的日志文件对所述受监控进程的应用程序或者设备进行恢复操作，其中，所述受监控进程的错误或异常信息引起所述受监控进程退出。
在其中的一个实施例中，所述创建日志文件保存所述受监控进程输出的日志信息之后，所述方法包括：
监控与所述受监控进程对应的所述配置文件中的第一文件的修改状况；
在所述修改状况为所述第一文件被正常修改的情况下，重新对所述配置文件中的第一文件进行校验核对，将重新校验后的第一文件备份到所述备份分区；
在所述修改状况为所述第一文件被非正常修改的情况下，用备份分区的第一备份文件覆盖所述第一文件。
在其中的一个实施例中，所述依据所述日志文件对所述受监控进程的应用程序或者设备进行恢复操作包括：
关闭与所述受监控进程对应的应用程序，根据所述日志文件重启与所述受监控进程对应的设备。
在其中的一个实施例中，所述依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行校验核对包括：
依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行信息摘要算法5(Message-Digest Algorithm，简称为MD5)校验核对。
在其中的一个实施例中，所述启动所述受监控进程包括：
通过pipe管道的方式启动所述受监控进程。
根据本申请的各种实施例，还提供一种程序进程监控的装置，所述装置包括：
校验模块，用于读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行校验核对，判断所述第一文件是否被非法修改；
数据备份恢复模块，用于在确定所述第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖所述第一文件；
创建模块，用于根据所述受监控进程的名称和参数信息，启动所述受监控进程，依据所述受监控进程的名称和当前时间，创建日志文件保存所述受监控进程输出的日志信息；
恢复模块，用于获取所述受监控进程退出的日志文件，依据所述受监控进程退出的日志文件对所述受监控进程的应用程序或者设备进行恢复操作，其中，所述受监控进程的错误或异常信息引起所述受监控进程退出。
在其中的一个实施例中，所述装置还包括：
数据备份模块，用于所述创建日志文件保存所述受监控进程输出的日志信息之后，监控与所述受监控进程对应的所述配置文件中的第一文件的修改状况，在所述修改状况为所述第一文件被正常修改的情况下，重新对所述配置文件中的第一文件进行校验核对，将重新校验后的第一文件备份到所述备份分区；在所述修改状况为所述第一文件被非正常修改的情况下，用备份分区的第一备份文件覆盖所述第一文件。
在其中的一个实施例中，所述恢复模块包括：
关闭重启单元，用于关闭与所述受监控进程对应的应用程序，根据所述日志文件重启与所述受监控进程对应的设备。
根据本申请的各种实施例，还提供一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现上述程序进程监控的方法的步骤。
根据本申请的各种实施例，还提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述程序进程监控的方法的步骤。
上述程序进程监控的方法、装置、计算机设备及可读存储介质具有以下优点：
读取程序监控的配置文件，依据该受监控进程的名称，对与该受监控进程对应的该配置文件中的第一文件进行校验核对，在确定该第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖该第一文件；依据该受监控进程的名称和当前时间，创建日志文件保存该受监控进程输出的日志信息；依据该日志文件对该受监控进程的应用程序或者设备进行恢复操作，解决了应用程序在操作系统中的进程如何有效及时监控的问题，保证了应用程序的稳定有序的运行。
附图说明
为了更好地描述和说明这里公开的那些发明的实施例和/或示例，可以参考一幅或多幅附图。用于描述附图的附加细节或示例不应当被认为是对所公开的发明、目前描述的实施例和/或示例以及目前理解的这些发明的最佳模式中的任何一者的范围的限制。
图1是本申请实施例的一种程序进程监控的方法应用环境的示意图。
图2是本申请实施例的一种程序进程监控的方法的流程图。
图3是本申请实施例的一种程序进程监控的装置的结构框图一。
图4是本申请实施例的一种程序进程监控的装置的结构框图二。
图5是本申请实施例的一种程序进程监控的装置的结构框图三。
图6是本申请实施例的基于嵌入式Linux系统对程序进程监控的方法的流程图。
具体实施方式
为了便于理解本申请，为使本申请的上述目的、特征和优点能够更加明显易懂，下面结合附图对本申请的具体实施方式做详细的说明。在下面的描述中阐述了很多具体细节以便于充分理解本申请，附图中给出了本申请的较佳实施方式。但是，本申请可以以许多不同的形式来实现，并不限于本文所描述的实施方式。相反地，提供这些实施方式的目的是使对本申请的公开内容理解的更加透彻全面。本申请能够以很多不同于在此描述的其它方式来实施，本领域技术人员可以在不违背本申请内涵的情况下做类似改进，因此本申请不受下面公开的具体实施例的限制。
此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。在本申请的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。在本申请的描述中，“若干”的含义是至少一个，例如一个，两个等，除非另有明确具体的限定。
除非另有定义，本文所使用的所有的技术和科学术语与属于本申请的技术领域的技术人员通常理解的含义相同。本文中所使用的术语只是为了描述具体的实施方式的目的，不是旨在于限制本申请。本文所使用的术语“及/或”包括一个或多个相关的所列项目的任意的和所有的组合。
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本申请的实施例提供的一种程序进程监控的方法，图1是本申请实施例的一种程序进程监控的方法应用环境的示意图，如图1所示，可以应用于程序进程监控的方法的应用环境中，其中，终端101通过网络与服务器102进行通信，其中，终端101可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备，服务器102可以用嵌入式设备服务器、独立的服务器或者是多个服务器组成的服务器集群来实现。终端101和服务器102安装的操作系统包括：嵌入式Linux系统、Unix系统、Windows系统、Android系统和Ios系统等，终端101和服务器102的操作系统均可以读取监控程序的配置文件，依据该受监控进程的名称，对与该受监控进程对应的该配置文件中的第一文件进行校验核对，在确定该第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖该第一文件；依据该受监控进程的名称和当前时间，创建日志文件保存该受监控进程输出的日志信息；依据该日 志文件对该受监控进程的应用程序或者设备进行恢复操作，解决了应用程序在操作系统中的进程如何有效及时监控的问题，保证了应用程序的稳定有序的运行。
在本申请的实施例中，提供了一种程序进程监控的方法，图2是本申请实施例的一种程序进程监控的方法的流程图，如图2所示，该方法包括如下步骤：
步骤S201：读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据该受监控进程的名称，对与该受监控进程对应的该配置文件中的第一文件进行校验核对，判断该第一文件是否被非法修改；
步骤S202：在确定该第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖该第一文件；
在本步骤中，嵌入式设备在突然断电情况下造成重要文件损坏或者人为非法修改文件都可以导致该第一文件被非法修改；
步骤S203：根据该受监控进程的名称和参数信息，启动该受监控进程，依据该受监控进程的名称和当前时间，创建日志文件保存该受监控进程输出的日志信息；
步骤S204：获取该受监控进程退出的该日志文件，依据该受监控进程退出的该日志文件对该受监控进程的应用程序或者设备进行恢复操作，其中，该受监控进程的错误或异常信息引起该受监控进程退出。
通过上述步骤，依据配置文件对受监控进程进行了校验，确定该受监控进程的启动，在启动之后，通过创建日志文件保存受监控进程的日志信息，在监控的程序的受监控进程的有错误和异常信息的情况下，通过该日志文件恢复监控的应用程序或者设备，解决了应用程序在操作系统中的进程如何有效及时监控的问题，保证了应用程序的稳定有序的运行。
在一个实施例中，一种实施方式中，监控程序在开始启动受监控进程之前，已经对配置文件进行了校验核对，有非法修改的情况下，已用第一备份文件覆盖第一文件，在没有非法修改的情况下，启动受监控进程之后，还要实时监控该受监控进程中的第一文件是否被修改，在接收到修改命令或修改通知后，该第一文件已经被正常修改，监控程序重新对该配置文件中的第一文件进行校验核对，并将该重新校验后的第一文件备份到该备份分区，另一个实施方式中，监控程序在开始启动受监控进程之前，已经对配置文件进行了校验核对，有非法修改的情况下，已用第一备份文件覆盖第一文件，启动受监控进程之后，还要实时监控该受监控进程中的第一备份文件是否被修改，在没有接收到修改命令或修改通知后，确定第一备份文件已经被非法修改，用备份分区中的第一备份文件覆盖该被非法修改后的第一备份文件，上述实施方式，在受监控进程运行之前和监控的过程中，均监控了配置文件是否被修改，实时监控了应用程序的配置文件是否被非法篡改。
在一个实施例中，根据该受监控进程的错误或异常信息引起该受监控进程退出的原因，对该受监控进程的应用程序或者设备进行恢复操作的方式会有不同，例如，受监控进程退出的原因仅仅和应用程序的有关，该恢复操作只要依据日志文件的记录，重启该应用程序就可以解决该程序故障，在受监控进程退出的原因可能是设备的硬件信息导致的，例如，内存的缓存错误情况，或者，无法判断是应用程序的问题还是设备硬件的问题的情况，或者，应用程序或者设备处于死循环的状态的情况，上述情况需要关闭与该受监控进程对应的应用程序，并根据该日志文件重启与该受监控进程对应的设备，上述日志文件的记录，还可以提供给维护人员，维护人员对监控的应用程序或者设备的故障参考数据统计后，根据受监控进程出现故障的频率、执行的程序任务或者时间节点信息等，分析出监控的应用程序开发过程中的错误，上述实施方式，可以在监控过程出现受监控进程退出的情况下，自启动应用程序或者设备，保证了应用程序运行的稳定性，另外，通过对日志文件记录的受监控进程退出原因的分析，为后续应用程序的修改提供了参考。
在一个实施例中，该依据该受监控进程的名称，对与该受监控进程对应的该配置文件中的第一文件进行校验核对的方式可以有多种，例如，依据该受监控进程的名称，对与该受监控进程对应的该配置文件中的第一文件进行信息摘要算法5(MD5)校验核对，对配置文件的第一文件进行MD5运算，得到的计算结果与预存的第一文件的校验码相比较，如果一致则第一文件没有被修改，否则认为第一文件被修改，需要用第一备份文件覆盖该第一文件，该检验核对的方式还可以包括信息摘要算法2(Message-Digest Algorithm 2，简称为MD2)和信息摘要算法4(Message-Digest Algorithm 4，简称为MD4)等。
在一个实施例中，嵌入式Linux系统中，启动该受监控进程的方式可以通过pipe管道的方式启动该受监控进程，还可以采用命名管道(First Input First Output，简称为FIFO)与信号管道(Signal)等方式启动该受监控进程，在受监控进程为第三方应用程序的情况下，优选采用pipe管道的方式启动该受监控进程。
对应于上述一种程序进程监控的方法，在本实施例中，还提供了一种程序进程监控的装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的设备较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
在一个实施例中，提供了一种程序进程监控的装置，图3是本申请实施例的一种程序进程监控的装置的结构框图一，如图3所示，该装置包括：
校验模块31，用于读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据该受监控进程的名称，对与该受监控进程对应的该配置文件中的第一文件进行校验核对，判 断该第一文件是否被非法修改；
数据备份恢复模块32，用于在确定该第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖该第一文件；
创建模块33，用于根据该受监控进程的名称和参数信息，启动该受监控进程，依据该受监控进程的名称和当前时间，创建日志文件保存该受监控进程输出的日志信息；
恢复模块34，用于获取该受监控进程退出的该日志文件，依据该受监控进程退出的该日志文件对该受监控进程的应用程序或者设备进行恢复操作，其中，该受监控进程的错误或异常信息引起该受监控进程退出。
通过上述装置，校验模块31和数据备份恢复模块32依据配置文件对受监控进程进行了校验，创建模块33确定该受监控进程的启动，在启动之后，通过创建日志文件保存受监控进程的日志信息，在监控的程序的受监控进程的有错误和异常信息的情况下，恢复模块34通过该日志文件恢复监控的应用程序或者设备，解决了应用程序在操作系统中的进程如何有效及时监控的问题，保证了应用程序的稳定有序的运行。
在一个实施例中，提供了一种程序进程监控的装置，图4是本申请实施例的一种程序进程监控的装置的结构框图二，如图4所示，该装置包括：
数据备份模块42，用于该创建日志文件保存该受监控进程输出的日志信息之后，监控与该受监控进程对应的该配置文件中的第一文件的修改状况，在该修改状况为该第一文件被正常修改的情况下，重新对该配置文件中的第一文件进行校验核对，将该重新校验后的第一文件备份到该备份分区；在该修改状况为该第一文件被非正常修改的情况下，用备份分区的第一备份文件覆盖该第一文件，将第一备份文件拷贝到该配置文件分区，保证受监控程序获取配置信息正确。
在一个实施例中，提供了一种程序进程监控的装置，图5是本申请实施例的一种程序进程监控的装置的结构框图三，如图5所示，该装置包括：
恢复模块38包括：关闭重启单元52，该关闭重启单元52用于关闭与该受监控进程对应的应用程序，根据该日志文件重启与该受监控进程对应的设备。
下面结合在应用场景对本申请的实施例进行详细说明，基于嵌入式Linux系统对程序进程监控的方法包含：进程监控，配置文件修改监控，备份及设备重启等，图6是根据本申请实施例的基于嵌入式Linux系统对程序进程监控的方法的流程图，如图6所示，该方法步骤包括：
步骤S601：读取监控程序配置文件，获取需要受监控进程名称及相关参数；
步骤S602：获取受监控进程名称后，对相应进程的配置文件夹相关文件进行MD5检验 核对，判断文件是否被非法修改；
步骤S603：若受监控进程的配置文件夹中有文件被非法修改，可能导致无法正常启动进程，则从备份分区中最新备份覆盖当前相关文件；
步骤S604：根据获取需要受监控进程名称及相关参数，通过pipe方式启动相应的受监控进程；
步骤S605：根据受监控进程是否输出log信息(日志文件信息)的需求，在相应log文件夹下创建以系统当前时间和进程名称log文件，用于保存受监控进程输出log信息；
步骤S606：监控程序实时对受监控进程相应的配置文件是否被修改。若文件被修改，需要对该文件重新校验，并将新文件备份到备份分区；
步骤S607：受监控进程在运行过程中，某个或某几个进程发生错误或异常导致进程退出，系统将会发送退出消息给监控程序，从而监控程序记录相关进程状态到本地log文件中，关闭相关应用后，重新启动设备。
通过上述方法步骤，Linux系统的监控程序完成了程序的进程监控、配置文件修改监控备份和设备重启的功能，解决了应用程序在Linux系统中的进程如何有效及时监控的问题，保证了应用程序的稳定有序的运行。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及优选实施例中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于光盘、软盘、硬盘、可擦写存储器等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一非易失性计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (10)

  1. 一种程序进程监控的方法，其特征在于，所述方法包括：
    读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行校验核对，判断所述第一文件是否被非法修改；
    在确定所述第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖所述第一文件；
    根据所述受监控进程的名称和参数信息，启动所述受监控进程，依据所述受监控进程的名称和当前时间，创建日志文件保存所述受监控进程输出的日志信息；
    获取所述受监控进程退出的日志文件，依据所述受监控进程退出的日志文件对所述受监控进程的应用程序或者设备进行恢复操作，其中，所述受监控进程的错误或异常信息引起所述受监控进程退出。
  2. 根据权利要求1所述方法，其特征在于，所述创建日志文件保存所述受监控进程输出的日志信息之后，所述方法包括：
    监控与所述受监控进程对应的所述配置文件中的第一文件的修改状况；
    在所述修改状况为所述第一文件被正常修改的情况下，重新对所述配置文件中的第一文件进行校验核对，将重新校验后的第一文件备份到所述备份分区；
    在所述修改状况为所述第一文件被非正常修改的情况下，用备份分区的第一备份文件覆盖所述第一文件。
  3. 根据权利要求1所述方法，其特征在于，所述依据所述日志文件对所述受监控进程的应用程序或者设备进行恢复操作包括：
    关闭与所述受监控进程对应的应用程序，根据所述日志文件重启与所述受监控进程对应的设备。
  4. 根据权利要求1至3任一项所述方法，其特征在于，所述依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行校验核对包括：
    依据所述受监控进程的名称，对与所述受监控进程对应的所述配置文件中的第一文件进行信息摘要算法5校验核对。
  5. 根据权利要求1至3任一项所述方法，其特征在于，所述启动所述受监控进程包括：
    通过pipe管道的方式启动所述受监控进程。
  6. 一种程序进程监控的装置，其特征在于，所述装置包括：
    校验模块，用于读取程序监控的配置文件，获取受监控进程的名称和参数信息，依据所 述受监控进程的名称，对与受所述受监控进程对应的所述配置文件中的第一文件进行校验核对，判断所述第一文件是否被非法修改；
    数据备份恢复模块，用于在确定所述第一文件被非法修改的情况下，用备份分区的第一备份文件覆盖所述第一文件；
    创建模块，用于根据所述受监控进程的名称和参数信息，启动所述受监控进程，依据所述受监控进程的名称和当前时间，创建日志文件保存所述受监控进程输出的日志信息；
    恢复模块，用于获取所述受监控进程退出的日志文件，依据所述受监控进程退出的日志文件对所述受监控进程的应用程序或者设备进行恢复操作，其中，所述受监控进程的错误或异常信息引起所述受监控进程退出。
  7. 根据权利要求6所述装置，其特征在于，所述装置还包括：
    数据备份模块，还用于所述创建日志文件保存所述受监控进程输出的日志信息之后，监控与所述受监控进程对应的所述配置文件中的第一文件的修改状况，在所述修改状况为所述第一文件被正常修改的情况下，重新对所述配置文件中的第一文件进行校验核对，将重新校验后的第一文件备份到所述备份分区；
    在所述修改状况为所述第一文件被非正常修改的情况下，用备份分区的第一备份文件覆盖所述第一文件。
  8. 根据权利要求6所述装置，其特征在于，所述恢复模块包括：
    关闭重启单元，用于关闭与所述受监控进程对应的应用程序，根据所述日志文件重启与所述受监控进程对应的设备。
  9. 一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其特征在于，所述处理器执行所述计算机程序时实现权利要求1至5中任一项所述方法的步骤。
  10. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至5中任一项所述的方法的步骤。
PCT/CN2020/117490 2019-09-26 2020-09-24 程序进程监控的方法、装置、计算机设备及可读存储介质 WO2021057855A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910918237.0 2019-09-26
CN201910918237.0A CN110851300A (zh) 2019-09-26 2019-09-26 程序进程监控的方法、装置、计算机设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2021057855A1 true WO2021057855A1 (zh) 2021-04-01

Family

ID=69596005

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117490 WO2021057855A1 (zh) 2019-09-26 2020-09-24 程序进程监控的方法、装置、计算机设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN110851300A (zh)
WO (1) WO2021057855A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110851300A (zh) * 2019-09-26 2020-02-28 三维通信股份有限公司 程序进程监控的方法、装置、计算机设备及可读存储介质
CN114356855A (zh) * 2021-12-06 2022-04-15 深圳市亚略特科技股份有限公司 文件管理方法、装置、电子装置及可读存储介质
CN117194110A (zh) * 2023-09-20 2023-12-08 通号通信信息集团上海有限公司 一种数据异构存储系统及异常数据自恢复方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102622290A (zh) * 2012-03-07 2012-08-01 苏州阔地网络科技有限公司 一种进程监控的方法及系统
US20120210198A1 (en) * 2011-02-16 2012-08-16 Invensys Systems Inc. System and Method for Fault Tolerant Computing Using Generic Hardware
CN104932965A (zh) * 2014-03-18 2015-09-23 北京奇虎科技有限公司 对象实时监控方法和装置
CN105045708A (zh) * 2015-09-02 2015-11-11 上海斐讯数据通信技术有限公司 软件运行错误处理方法及系统
CN107423620A (zh) * 2017-03-12 2017-12-01 郑州云海信息技术有限公司 存储服务器服务进程的管理方法及装置
CN110851300A (zh) * 2019-09-26 2020-02-28 三维通信股份有限公司 程序进程监控的方法、装置、计算机设备及可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7114097B2 (en) * 2003-12-19 2006-09-26 Lenovo (Singapore) Pte. Ltd. Autonomic method to resume multi-threaded preload imaging process
US20070256082A1 (en) * 2006-05-01 2007-11-01 International Business Machines Corporation Monitoring and controlling applications executing in a computing node
CN101231682B (zh) * 2007-01-26 2011-01-26 李贵林 计算机信息安全的方法
CN101227630A (zh) * 2008-01-29 2008-07-23 中兴通讯股份有限公司 一种基于窗口平台的应用程序监控方法
CN104239095A (zh) * 2014-09-01 2014-12-24 小米科技有限责任公司 操作系统启动方法、装置及终端设备
CN106775981B (zh) * 2016-12-15 2020-03-03 北京奇虎科技有限公司 一种进程处理方法、装置及计算机可读介质
CN107678878A (zh) * 2017-10-12 2018-02-09 郑州云海信息技术有限公司 一种异常进程的处理方法及装置
CN110187996A (zh) * 2019-05-30 2019-08-30 苏州浪潮智能科技有限公司 Bmc主进程故障诊断方法、装置、设备及可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120210198A1 (en) * 2011-02-16 2012-08-16 Invensys Systems Inc. System and Method for Fault Tolerant Computing Using Generic Hardware
CN102622290A (zh) * 2012-03-07 2012-08-01 苏州阔地网络科技有限公司 一种进程监控的方法及系统
CN104932965A (zh) * 2014-03-18 2015-09-23 北京奇虎科技有限公司 对象实时监控方法和装置
CN105045708A (zh) * 2015-09-02 2015-11-11 上海斐讯数据通信技术有限公司 软件运行错误处理方法及系统
CN107423620A (zh) * 2017-03-12 2017-12-01 郑州云海信息技术有限公司 存储服务器服务进程的管理方法及装置
CN110851300A (zh) * 2019-09-26 2020-02-28 三维通信股份有限公司 程序进程监控的方法、装置、计算机设备及可读存储介质

Also Published As

Publication number Publication date
CN110851300A (zh) 2020-02-28

Similar Documents

Publication Publication Date Title
WO2021057855A1 (zh) 程序进程监控的方法、装置、计算机设备及可读存储介质
CN106716972B (zh) 半自动故障转移
US20170116084A1 (en) Method and System for Monitoring Virtual Machine Cluster
US7356744B2 (en) Method and system for optimizing testing of memory stores
CN112035472B (zh) 数据处理方法、装置、计算机设备和存储介质
US10853180B2 (en) Automatically setting a dynamic restore policy in a native cloud environment
US9164857B2 (en) Scalable structured data store operations
CN107453932B (zh) 一种分布式存储系统管理方法及其装置
CN111104238B (zh) 一种基于ce的内存诊断的方法、设备及介质
CN108932249B (zh) 一种管理文件系统的方法及装置
RU2646309C1 (ru) Способ резервного копирования
CN111901176B (zh) 故障确定方法、装置、设备及存储介质
CN110990124A (zh) 云主机恢复方法和装置
CN105550071A (zh) 系统文件升级及检测方法、通信设备
CN115080340A (zh) 软磁盘阵列监控方法、系统、计算机设备和存储介质
TW201510995A (zh) 維護電腦系統之檔案系統的方法
CN113691395A (zh) 网络运维方法、装置、计算机设备和存储介质
CN116010199A (zh) 应用服务自调节方法、装置、计算机设备及存储介质
CN114490196A (zh) 数据库切换方法、系统、设备及介质
CN110968456A (zh) 分布式存储系统中故障磁盘的处理方法及装置
CN113721746A (zh) 一种日志的存储方法及装置
CN111985010A (zh) 笔记本硬盘的拦截校验方法、装置、计算机设备及存储介质
CN111460035A (zh) 一种数据库系统及其容灾方法
CN109933351A (zh) 一种修复和升级Linux系统的方法与装置
CN117033086B (zh) 操作系统的恢复方法、装置、存储介质和服务器管理芯片

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20868367

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20868367

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20868367

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.10.2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20868367

Country of ref document: EP

Kind code of ref document: A1