CN107729213A - A kind of background task monitoring method and device - Google Patents
A kind of background task monitoring method and device Download PDFInfo
- Publication number
- CN107729213A CN107729213A CN201710941181.1A CN201710941181A CN107729213A CN 107729213 A CN107729213 A CN 107729213A CN 201710941181 A CN201710941181 A CN 201710941181A CN 107729213 A CN107729213 A CN 107729213A
- Authority
- CN
- China
- Prior art keywords
- background task
- task
- background
- monitor
- monitoring
- 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
Classifications
-
- 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/3017—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is implementing multitasking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3096—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
This application discloses a kind of background task monitoring method and device, and applied to the network equipment, the network equipment has run monitor task corresponding with background task, and method therein includes:The monitor task periodically reads the background task that run-stopping status are marked as in background task monitoring inventory;Wherein, the background task monitoring inventory includes api interface corresponding with background task;Api interface corresponding with the background task is called to determine whether the background task needs to start;If it is, start the background task.This programme can avoid the wasting of resources of system.
Description
Technical field
The application is related to computer realm, more particularly to a kind of background task monitoring method and device.
Background technology
In existing operating system, multiple background tasks can be generally run simultaneously.Background task is not usually required to reality
When interacted with user, that is to say, that background task can be not present in the visual interface of user and only be provided on backstage
Service, the service specifically provided can be periodically monitoring, timed reminding, Service-Port monitoring, be periodically detected mainboard and
Too high warning function of cpu temperature etc..In actual moving process, background task may due to program mal, system is unstable, net
Network Message processing error etc. a series of reasons and it is out of service.Because background task does not control terminal accordingly, user is usual
It can not directly find that background task has terminated, it is therefore desirable to which taking some measures ensures that background task can weigh after terminating to run
It is new to start, continue to provide original function to system.
In the prior art, main stream approach is directly to establish monitor task with background task to communicate, and is appointed when listening to backstage
Business starts the task when stopping.The method for establishing communication is broadly divided into by heartbeat message and realized by poll.
When monitor task is by monitoring the heartbeat message of background task directly to be communicated with background task, if one
Interior monitor task of fixing time does not receive the heartbeat message of background task transmission, it is determined that the background task is out of service, prison
Control task starts the background task according to default Starting mode corresponding with the background task.
When monitor task is directly communicated by the method for poll with background task, monitor task can generate one
Background task monitors inventory, is often gone in the inventory and corresponds to a background task, and the background task title can be included in often going, is opened
Flowing mode and store task identification ID file (PID files) routing information.Wherein, each background task is in initial start
When oneself task identification ID is write in corresponding PID files.Monitor task is clear by periodicity traversal background task monitoring
Single, whether for every a line, checking has task identification ID to be equal to times that PID document memories in the row store up in the background task of operation
Business mark ID, illustrates the task still in running status if having;If illustrating that the task is out of service without if, retouched according to the row
The Starting mode stated starts the background task.
In the prior art, monitor task directly initiates the backstage times for being marked as run-stopping status to above two main flow
Business, and not be made whether to need the judgement started, this may cause system resource waste.
The content of the invention
The application provides a kind of background task monitoring method, it is characterised in that applied to the network equipment, the network equipment
Monitor task corresponding with background task has been run, including:
The monitor task periodically reads the backstage times that run-stopping status are marked as in background task monitoring inventory
Business;Wherein, the background task monitoring inventory includes api interface corresponding with background task;
Api interface corresponding with the background task is called to determine whether the background task needs to start;
If it is, start the background task.
Optionally, the network equipment is equipped with scheduler program;It is corresponding with background task that the scheduler program is used for execution
Task termination flow;Also include:
The scheduler program listens to background task event message out of service;
In response to the event message, background task notification message out of service is issued to the monitor task.
Optionally, the monitor task periodically reads in background task monitoring inventory and is marked as run-stopping status
Background task, including:
Receive the notification message that the scheduler program issues;
In response to the notification message, periodically read in background task monitoring inventory and be marked as run-stopping status
Background task.
Optionally, the background task monitoring inventory includes Starting mode corresponding with background task;The startup includes:
Starting mode corresponding with the background task is inquired about in platform Mission Monitor inventory in the rear;
The background task is started based on the Starting mode inquired.
Optionally, methods described also includes:
After the background task is started, the generation journal file related to background task startup;
The journal file of generation is reported.
The application also provides a kind of background task supervising device, applied to the network equipment, the network equipment run with
Monitor task corresponding to background task, including:
Monitoring module, it is out of service for being marked as in the monitor task periodically reading background task monitoring inventory
The background task of state;Wherein, the background task monitoring inventory includes api interface corresponding with background task;
Determining module, for calling api interface corresponding with the background task to determine whether the background task needs
Start;
Starting module, if necessary to start, for starting the background task.
Optionally, described device also includes:
Scheduler module, the event message out of service for listening to the background task;
In response to the event message, background task notification message out of service is issued to the monitor task.
Optionally, the monitoring module is further used for:
Receive the notification message that the scheduler module issues;
In response to the notification message, periodically read in background task monitoring inventory and be marked as run-stopping status
Background task.
Optionally, the background task monitoring inventory includes Starting mode corresponding with background task;The starting module
It is further used for:
Starting mode corresponding with the background task is inquired about in platform Mission Monitor inventory in the rear;
The background task is started based on the Starting mode inquired.
Optionally, described device also includes:
Reporting module, it is used for
After the background task is started, the generation journal file related to background task startup;
The journal file of generation is reported.
In the method that the application provides, the monitor task periodically reads in background task monitoring inventory and is marked as stopping
The only background task of running status;Wherein, the background task monitoring inventory includes api interface corresponding with background task;Adjust
With api interface corresponding with the background task to determine whether the background task needs to start;If it is, after startup is described
Platform task.
In this programme, because before startup is marked as the background task of run-stopping status, monitor task is connect by API
Mouthful to whether needing to start the background task and judging, so as to avoid the wasting of resources of system.
Brief description of the drawings
, below will be to embodiment or existing in order to illustrate more clearly of the embodiment of the present application or technical scheme of the prior art
There is the required accompanying drawing used in technology description to be briefly described, it should be apparent that, come for those of ordinary skill in the art
Say, other accompanying drawings can also be obtained according to these accompanying drawings.
Fig. 1 is a kind of flow chart for background task monitoring method that the embodiment of the application one provides;
Fig. 2 is a kind of signaling process figure of background task monitoring method;
Fig. 3 is the signaling process figure of another background task monitoring method;
Fig. 4 is a kind of signaling process figure for background task monitoring method that the embodiment of the application one provides;
Fig. 5 is a kind of logic diagram for background task supervising device that the embodiment of the application one provides;
Fig. 6 is carrying a kind of hardware of the network equipment of background task supervising device that the embodiment of the application one provides
Structure chart.
Embodiment
In the prior art, it is main logical to realize the background task stopped in restarting operating systems by accidental cause
The mode that monitor task and background task are directly established to communication is crossed, restarts this when listening to background task and stopping
Business.Wherein, the method for establishing communication is broadly divided into by heartbeat message and realized by poll.
Above-mentioned monitor task can be understood as the background task started in operating system, for other background tasks
It is monitored.
Scheduler program can also be included in aforesaid operations system, the scheduler program can be understood as being buffered in operating system
In one section be used to performing the code of background task management, can all pass through calling at the end of all background tasks in operating system
The scheduler program performs task termination flow, and the task termination flow includes Resource recovery (internal memory, file, task ID
Deng), close external connection, delete temporary file etc..In device item, the scheduler module, which can be equal, to be interpreted as dispatching journey
Sequence.
When monitor task is by monitoring the heartbeat message of background task directly to be communicated with background task, refer to
Fig. 2, Fig. 2 are the signaling process figure of the background task monitoring method.Wherein, background task periodically sends heartbeat to monitor task
Message, if monitor task does not receive the heartbeat message of background task transmission in certain time, it is determined that the background task is
Out of service, monitor task starts the background task according to default Starting mode corresponding with the background task.
When monitor task is directly communicated by the method for poll with background task, Fig. 3 is refer to, Fig. 3 is after this
The signaling process figure of platform Mission Monitor method.Wherein, monitor task can generate a background task monitoring inventory, refer to table
1, table 1 is that a kind of background task shown in prior art monitors inventory, is often gone in the inventory and corresponds to a background task, often row can
With the road of the task names including corresponding background task, Starting mode and the file (PID files) for storing task identification ID
Footpath information.Wherein, each background task writes the task identification ID of oneself in corresponding PID files in initial start.Monitoring
Task monitors inventory by periodicity traversal background task, for every a line, checks in the background task of operation whether there is task
Identify ID and be equal to the task identification ID that PID document memories store up in the row, illustrate the task still in running status if having;If nothing
Then illustrate that the task is out of service, the background task is started according to the Starting mode that the row describes.Supervised by the background task
Inventory is controlled, monitor task can realize the real-time monitoring to background task.
It is above-mentioned that monitor task directly initiates the background task for being marked as run-stopping status in the prior art, and not
It is made whether to need the judgement started, this may cause system resource waste.
Task names | Starting mode | PID file path information |
cpu_monitor | /usr/bin/cpu_monitor-d | /var/run/cpu_monitor.pid |
Table 1
In view of considerations above, the application proposes a kind of background task monitoring method.In the method that the application provides, the prison
Control duty cycle reads the background task that run-stopping status are marked as in background task monitoring inventory;Wherein, after described
Platform Mission Monitor inventory includes api interface corresponding with background task;Api interface corresponding with the background task is called with true
Whether the fixed background task needs to start;If it is, start the background task.
In this programme, because before startup is marked as the background task of run-stopping status, monitor task is connect by API
Mouthful to whether needing to start the background task and judging, so as to avoid the wasting of resources of system.
The application is described below by specific embodiment and with reference to specific application scenarios.
Refer to Fig. 1, Fig. 1 is a kind of background task monitoring method that the embodiment of the present application provides, applied to the network equipment,
The network equipment has run monitor task corresponding with background task, performs following steps:
S101, the monitor task is periodically read be marked as run-stopping status in background task monitoring inventory after
Platform task;Wherein, the background task monitoring inventory includes api interface corresponding with background task;
S102, api interface corresponding with the background task is called to determine whether the background task needs to start;
S103, if it is, starting the background task.
The above-mentioned network equipment can include the common apparatus that arbitrary form is equipped with operating system;For example, it may be installation
There are personal computer, server of operating system etc..
Above-mentioned api interface can be the interface function provided by background task, and the interface function, which can be used for judgement, is
It is no to start background task corresponding with the interface function.Wherein, the api interface is connect by corresponding with the api interface
What mouthful call method was called, the call method is realized based on programming language and implementation has a variety of, and is not had to
To limit the present invention.
Fig. 4 is refer to, Fig. 4 is a kind of signaling process figure for background task monitoring method that the present embodiment provides.
In this example, monitor task can generate background task monitoring inventory, refer to table 2, and table 2 is shown in the present embodiment
A kind of background task monitors inventory, and the inventory can include all background tasks run in operating system;Wherein, the backstage is appointed
The corresponding background task of every a line of business monitoring inventory, and the task name that the row corresponds to background task can be included per a line
Title, task status, Starting mode and api interface.Inventory is monitored by the background task, the monitor task can be to backstage
Task is managed and updated.
Task names | Task status | Starting mode | Api interface |
cpu_monitor | Operation/stopping | /usr/bin/cpu_monitor-d | check_cpu_monitor_state |
Table 2
In this example, operating system also includes scheduler program, and the task termination flow performed by scheduler program is in existing skill
The event that monitoring task terminates operation is added on the basis of art.Scheduler program monitors background task in real time, when the scheduling journey
Sequence listens to background task event out of service, and scheduler program is used for monitor task notification message transmission, the notification message
Indicate that the background task is out of service.
In this way, because scheduler program prison is when hearing that background task is out of service, can just appoint to the monitoring
Business issues background task notification message out of service, avoids big between monitor task and background task in the prior art
Amount communication, so as to avoid the waste of system resource.
In this example, the monitor task is after the notification message that the scheduler program is sent is received, after having generated
The background task for indicating the message in platform Mission Monitor inventory is labeled as run-stopping status.
In this example, the monitor task can periodically travel through the background task monitoring inventory, and read background task
The background task of run-stopping status is marked as in inventory.
In this example, after the background task of run-stopping status is marked as described in reading out, the monitor task is adjusted
With api interface corresponding with the background task, determine whether the background task needs to start.
Wherein, the api interface can determine and the API according to situations such as system type, deployable state, configuration data
Whether background task corresponding to interface, which needs, starts.It is understood that due to system type, deployable state, configuration data this
A little Rule of judgment are extremely complex and flexible and changeable, therefore above-mentioned example is only schematical, can not be limiting the present invention.
In this way, on the one hand because before startup is marked as the background task of run-stopping status, monitoring is appointed
Business by api interface to whether needing to start the background task and judging, so as to avoid the wasting of resources of system.
On the other hand, because monitor task is realized by api interface, therefore it is corresponding to change background task
Source code, realize relatively simple;It it also avoid using PID multiplying questions caused by PID in the prior art.
In a kind of embodiment shown, the backstage that the backstage by tag splice mouth is run-stopping status is being read out
After task, the monitor task first passes through inspection policy and existed to be marked as the background task of run-stopping status described in determining
Whether it is currently running in operating system, when it is determined that the background task for being marked as run-stopping status is not run, then passes through
Interface function corresponding with the background task is called to determine whether the background task needs to start.
Wherein, the inspection policy can include:
In an operating system, the monitor task inquiry is labeled with the presence or absence of the title of being currently running for task with described
Title for the task of run-stopping status is identical;
If it is not present, it is determined that the task is out of service in an operating system;
It is on the contrary, it is determined that the task is currently running in an operating system.
By this embodiment, the interference of some specific factors can be excluded, for example, in the monitor task twice time
In the time interval gone through, the background task for being marked as run-stopping status is restarted by other means;Its
In, other modes can be that system maintenance personnel manually boot to the background task.
In this example, if it is determined that the background task needs to start, then is inquired about in the rear in platform Mission Monitor inventory
Starting mode corresponding with the background task, and the background task is started based on the Starting mode inquired.
In this example, the monitor task can also generate and the background task after the background task is restarted
Start related journal file, and the journal file generated carried out to report service end, to allow keeper to pass through
The journal file that stores is accessed in service end to find the reason for background task is out of service, and solves problem.Wherein, institute
When the task names of the background task, Startup time, last time operation can be included by stating the file related to background task startup
Between, it is out of service the reason for etc..
In the method that the application provides, the monitor task periodically reads in background task monitoring inventory and is marked as stopping
The only background task of running status;Wherein, the background task monitoring inventory includes api interface corresponding with background task;Adjust
With api interface corresponding with the background task to determine whether the background task needs to start;If it is, after startup is described
Platform task.
In this programme, because before startup is marked as the background task of run-stopping status, monitor task is connect by API
Mouthful to whether needing to start the background task and judging, so as to avoid the wasting of resources of system.
Corresponding with above method embodiment, present invention also provides the embodiment of device.
Fig. 5 is refer to, Fig. 5 is a kind of background task supervising device 50 that the embodiment of the application one provides, applied to network
Equipment;Wherein, Fig. 6 is refer to, as the hardware structure carried involved by the network equipment of the background task supervising device 50
In, generally include CPU, internal memory, nonvolatile memory and internal bus etc.;Exemplified by implemented in software, the background task
Supervising device 50 is generally understood that the computer program being carried in internal memory, the software and hardware formed afterwards by CPU operations
The logic device being combined, the background task supervising device 50, applied to the network equipment, the network equipment run with it is rear
Monitor task corresponding to platform task, described device include:
Monitoring module 501, periodically read for the monitor task in background task monitoring inventory and be marked as stopping
The background task of running status;Wherein, the background task monitoring inventory includes api interface corresponding with background task;
Determining module 502, for calling api interface corresponding with the background task whether to determine the background task
Need to start;
Starting module 503, if necessary to start, for starting the background task.
In this example, described device also includes:
Scheduler module 505, the event message out of service for listening to the background task;
In response to the event message, background task notification message out of service is issued to the monitor task.
In this example, the monitoring module is further used for:
Receive the notification message that the scheduler module issues;
In response to the notification message, periodically read in background task monitoring inventory and be marked as run-stopping status
Background task.
In this example, the background task monitoring inventory includes Starting mode corresponding with background task;The startup mould
Block is further used for:
Starting mode corresponding with the background task is inquired about in platform Mission Monitor inventory in the rear;
The background task is started based on the Starting mode inquired.
In this example, described device also includes:
Reporting module 504, is used for
After the background task is started, the generation journal file related to background task startup;
The journal file of generation is reported.
For device embodiment, because it corresponds essentially to embodiment of the method, so related part is real referring to method
Apply the part explanation of example.Device embodiment described above is only schematical, wherein described be used as separating component
The unit of explanation can be or may not be physically separate, can be as the part that unit is shown or can also
It is not physical location, you can with positioned at a place, or can also be distributed on multiple NEs.Can be according to reality
Need to select some or all of module therein to realize the purpose of application scheme.Those of ordinary skill in the art are not paying
In the case of going out creative work, you can to understand and implement.
The preferred embodiment of the application is the foregoing is only, not limiting the application, all essences in the application
God any modification, equivalent substitution and improvements done etc., should be included within the scope of the application protection with principle.
Claims (10)
1. a kind of background task monitoring method, it is characterised in that applied to the network equipment, the network equipment has been run and backstage
Monitor task corresponding to task, including:
The monitor task periodically reads the background task that run-stopping status are marked as in background task monitoring inventory;Its
In, the background task monitoring inventory includes api interface corresponding with background task;
Api interface corresponding with the background task is called to determine whether the background task needs to start;
If it is, start the background task.
2. according to the method for claim 1, it is characterised in that the network equipment is equipped with scheduler program;The scheduling
Program is used to perform task termination flow corresponding with background task;
Also include:
The scheduler program listens to background task event message out of service;
In response to the event message, background task notification message out of service is issued to the monitor task.
3. according to the method for claim 2, it is characterised in that it is clear that the monitor task periodically reads background task monitoring
The background task of run-stopping status is marked as in list, including:
Receive the notification message that the scheduler program issues;
In response to the notification message, the backstage that run-stopping status are marked as in background task monitoring inventory is periodically read
Task.
4. according to the method for claim 1, it is characterised in that the background task monitoring inventory includes and background task pair
The Starting mode answered;The startup includes:
Starting mode corresponding with the background task is inquired about in platform Mission Monitor inventory in the rear;
The background task is started based on the Starting mode inquired.
5. according to the method for claim 1, it is characterised in that also include:
After the background task is started, the generation journal file related to background task startup;
The journal file of generation is reported.
6. a kind of background task supervising device, it is characterised in that applied to the network equipment, the network equipment has been run and backstage
Monitor task corresponding to task, including:
Monitoring module, periodically read for the monitor task in background task monitoring inventory and be marked as run-stopping status
Background task;Wherein, the background task monitoring inventory includes api interface corresponding with background task;
Determining module, for calling api interface corresponding with the background task to determine whether the background task needs to open
It is dynamic;
Starting module, if necessary to start, for starting the background task.
7. device according to claim 6, it is characterised in that also include:
Scheduler module, the event message out of service for listening to the background task;
In response to the event message, background task notification message out of service is issued to the monitor task.
8. device according to claim 7, it is characterised in that the monitoring module is further used for:
Receive the notification message that the scheduler module issues;
In response to the notification message, the backstage that run-stopping status are marked as in background task monitoring inventory is periodically read
Task.
9. device according to claim 6, it is characterised in that the background task monitoring inventory includes and background task pair
The Starting mode answered;The starting module is further used for:
Starting mode corresponding with the background task is inquired about in platform Mission Monitor inventory in the rear;
The background task is started based on the Starting mode inquired.
10. device according to claim 6, it is characterised in that also include:
Reporting module, it is used for
After the background task is started, the generation journal file related to background task startup;
The journal file of generation is reported.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710941181.1A CN107729213B (en) | 2017-10-11 | 2017-10-11 | Background task monitoring method and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710941181.1A CN107729213B (en) | 2017-10-11 | 2017-10-11 | Background task monitoring method and device |
Publications (2)
Publication Number | Publication Date |
---|---|
CN107729213A true CN107729213A (en) | 2018-02-23 |
CN107729213B CN107729213B (en) | 2022-04-26 |
Family
ID=61210299
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710941181.1A Active CN107729213B (en) | 2017-10-11 | 2017-10-11 | Background task monitoring method and device |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN107729213B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110297741A (en) * | 2019-06-24 | 2019-10-01 | 杭州迪普信息技术有限公司 | A kind of background task monitoring method and device |
CN110321206A (en) * | 2019-06-26 | 2019-10-11 | 北京金山安全软件有限公司 | Service management method, device, electronic equipment and storage medium |
CN113810250A (en) * | 2021-09-27 | 2021-12-17 | 西安热工研究院有限公司 | Message tracking method, system and equipment |
US11392411B2 (en) | 2019-11-08 | 2022-07-19 | Sap Se | Background job scheduling restrictions |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2375633A (en) * | 2001-03-15 | 2002-11-20 | Hewlett Packard Co | Redundant controller data storage system having hot insertion system and method |
CN102103676A (en) * | 2011-02-28 | 2011-06-22 | 南京邮电大学 | Method for protecting Java program progress based on inheritance relationship among progresses |
CN103678084A (en) * | 2012-09-21 | 2014-03-26 | 成都勤智数码科技股份有限公司 | Flexible application process guarding method |
CN103870747A (en) * | 2014-03-31 | 2014-06-18 | 可牛网络技术(北京)有限公司 | Method and device for monitoring and processing application program |
CN105095046A (en) * | 2015-07-14 | 2015-11-25 | 北京奇虎科技有限公司 | Method and device for task monitoring |
CN105354131A (en) * | 2015-12-11 | 2016-02-24 | 北京慧眼智行科技有限公司 | Monitoring method for running of service program and device |
-
2017
- 2017-10-11 CN CN201710941181.1A patent/CN107729213B/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2375633A (en) * | 2001-03-15 | 2002-11-20 | Hewlett Packard Co | Redundant controller data storage system having hot insertion system and method |
CN102103676A (en) * | 2011-02-28 | 2011-06-22 | 南京邮电大学 | Method for protecting Java program progress based on inheritance relationship among progresses |
CN103678084A (en) * | 2012-09-21 | 2014-03-26 | 成都勤智数码科技股份有限公司 | Flexible application process guarding method |
CN103870747A (en) * | 2014-03-31 | 2014-06-18 | 可牛网络技术(北京)有限公司 | Method and device for monitoring and processing application program |
CN105095046A (en) * | 2015-07-14 | 2015-11-25 | 北京奇虎科技有限公司 | Method and device for task monitoring |
CN105354131A (en) * | 2015-12-11 | 2016-02-24 | 北京慧眼智行科技有限公司 | Monitoring method for running of service program and device |
Non-Patent Citations (1)
Title |
---|
王虹宇著: "《Linux服务器管理员教程》", 31 January 2001 * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110297741A (en) * | 2019-06-24 | 2019-10-01 | 杭州迪普信息技术有限公司 | A kind of background task monitoring method and device |
CN110297741B (en) * | 2019-06-24 | 2022-11-25 | 杭州迪普信息技术有限公司 | Background task monitoring method and device |
CN110321206A (en) * | 2019-06-26 | 2019-10-11 | 北京金山安全软件有限公司 | Service management method, device, electronic equipment and storage medium |
US11392411B2 (en) | 2019-11-08 | 2022-07-19 | Sap Se | Background job scheduling restrictions |
CN113810250A (en) * | 2021-09-27 | 2021-12-17 | 西安热工研究院有限公司 | Message tracking method, system and equipment |
CN113810250B (en) * | 2021-09-27 | 2023-02-07 | 西安热工研究院有限公司 | Message tracking method, system and equipment |
Also Published As
Publication number | Publication date |
---|---|
CN107729213B (en) | 2022-04-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6669682B2 (en) | Cloud server scheduling method and apparatus | |
CN108874558B (en) | Message subscription method of distributed transaction, electronic device and readable storage medium | |
US20110196957A1 (en) | Real-Time Policy Visualization by Configuration Item to Demonstrate Real-Time and Historical Interaction of Policies | |
CN107729213A (en) | A kind of background task monitoring method and device | |
CN111786886B (en) | Message processing method, device and system, electronic equipment and storage medium | |
CN112000350B (en) | Dynamic rule updating method, device and storage medium | |
CN107819640B (en) | Monitoring method and device for robot operating system | |
CN109783151B (en) | Method and device for rule change | |
CN109298948B (en) | Distributed computing method and system | |
CN112905323B (en) | Data processing method, device, electronic equipment and storage medium | |
CN108255628A (en) | A kind of data processing method and device | |
CN112182089B (en) | Report generation method, device and equipment based on data warehouse model | |
CN115328741A (en) | Exception handling method, device, equipment and storage medium | |
CN111880948A (en) | Data refreshing method and device, electronic equipment and computer readable storage medium | |
CN114168297A (en) | Method, device, equipment and medium for scheduling collection tasks | |
CN110188258B (en) | Method and device for acquiring external data by using crawler | |
CN105871659A (en) | Monitoring method and device of newly added server | |
CN110297706A (en) | A kind of inserting method based on Eureka-Server project | |
CN105338058A (en) | Application updating method and device | |
CN111290873B (en) | Fault processing method and device | |
CN113127158B (en) | Method and device for executing data processing task | |
CN112860292A (en) | Configuration management method and device based on application | |
CN112559001B (en) | Method and device for updating application | |
CN113626379A (en) | Research and development data management method, device, equipment and medium | |
CN112672369A (en) | Electronic price tag management method, server and computer 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 |