CN113688106A - File monitoring method and device - Google Patents
File monitoring method and device Download PDFInfo
- Publication number
- CN113688106A CN113688106A CN202111251303.7A CN202111251303A CN113688106A CN 113688106 A CN113688106 A CN 113688106A CN 202111251303 A CN202111251303 A CN 202111251303A CN 113688106 A CN113688106 A CN 113688106A
- Authority
- CN
- China
- Prior art keywords
- event
- information
- file
- path information
- task queue
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
Abstract
The application provides a file monitoring method and device, and belongs to the technical field of data processing. The method comprises the following steps: determining the event type according to the obtained file information of the current event; the file information includes: system information ino, path information, modification time information and father directory information; when the event type is a file adding event or a folder adding event, determining an event subtype based on file information; when the event type is a file deleting event or a folder deleting event, judging whether a task queue contains a task of the path information of the current event or not, and determining the event subtype. The method and the device solve the problems that monitoring effect is inaccurate and multiple triggers can occur due to file change monitoring in the prior art, and can monitor renaming and moving events.
Description
Technical Field
The invention belongs to the technical field of data processing, and particularly relates to a method and a device for file monitoring based on chokdar and sqlite 3.
Background
The prior art uses node own fs.watch and fs.watch File to listen to the changes of the file: the method comprises the following steps: file operations such as deletion, addition, modification, renaming, movement and the like of the file.
In the prior art, a node is used for monitoring file change by using fs.watch and fs.watch File, and the defects are that the monitoring effect is inaccurate and can be triggered for multiple times; however, chokdar and node-watch cannot listen for rename and move events.
Disclosure of Invention
The embodiment of the invention aims to provide a file monitoring method and device, and solves the problem that renaming and mobile events cannot be monitored in the prior art.
In order to achieve the above object, an embodiment of the present invention provides a file listening method, including:
determining the event type according to the obtained file information of the current event; the file information includes: event type identification, system information ino, path information, modification time information and father directory information;
when the event type is a file adding event or a folder adding event, determining an event subtype based on file information, wherein the event subtype comprises a renaming event or a moving event;
when the event type is a file deleting event or a folder deleting event, judging whether a task queue contains a task of the path information of the current event or not, and determining the event subtype.
An embodiment of the present invention further provides a file monitoring apparatus, including:
the first determining module is used for determining the event type according to the obtained file information of the current event; the file information includes: event type identification, system information ino, path information, modification time information and father directory information;
the second determination module is used for determining an event subtype based on the file information when the event type is a file adding event or a folder adding event, wherein the event subtype comprises a renaming event or a moving event;
and the third determining module is used for judging whether the task queue contains the task of the path information of the current event or not and determining the event subtype when the event type is a file deleting event or a folder deleting event.
Determining an event type according to the obtained file information of the event; when the event type is a file adding event or a folder adding event, determining an event subtype based on file information; when the event type is a file deleting event or a folder deleting event, judging whether a task queue contains a task of the file information of the current event or not, and determining an event subtype. This application has been solved prior art and has used node from fs.watch and fs.watch File to monitor the file change, and the monitoring effect is inaccurate, problem that can trigger many times can utilize the node to use the rename of folder and the monitoring of removal.
Drawings
FIG. 1 is a flow chart illustrating the initial steps provided by an embodiment of the present invention;
FIG. 2 is a flowchart illustrating steps of a file listening method according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating steps for adding a file event according to an embodiment of the present invention;
FIG. 4 is a flowchart of the steps provided by an embodiment of the present invention to add a folder event;
FIG. 5 is a flowchart illustrating the steps of a delete file event according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating the steps of a delete folder event according to an embodiment of the present invention;
FIG. 7 is a flowchart of the steps for a file content change event provided by an embodiment of the present invention;
fig. 8 is a block diagram of a file monitoring apparatus according to an embodiment of the present invention;
fig. 9 is a block diagram of a file listening device according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the description is intended to be exemplary only, and is not intended to limit the scope of the present invention. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present invention.
Js-based module for monitoring folder changes, and is used for monitoring changes of files such as movement, addition, deletion, change and the like.
The system information ino represents the file ino attribute acquired through fs.stat, is position information stored in the file, does not change after renaming or moving, and is mainly used for judging whether the file is the same file after renaming.
Fig. 1 shows a flowchart of the starting steps provided by the embodiment of the present invention, as shown in fig. 1, a snooping path of a folder is registered by using a cookie, a local disk is scanned by the registry, the scanned file information is obtained by a stat method of fs and is stored in a sqlite3 database, and a rename event or a move event is determined by using system information ino and path information of a file during snooping.
In this embodiment, a file listening method is provided, and fig. 2 is a flowchart of the file listening method according to the embodiment of the present application, and as shown in fig. 2 and fig. 7, the flowchart includes the following steps:
step S201, determining an event type according to the obtained file information of the current event; the file information includes: event type identification, system information ino, path information, modification time information and father directory information;
for example, the file information includes an event type identifier in addition to system information ino, path information, modification time information, and parent directory information, and the determining of the event type according to the obtained file information of the event specifically includes: and determining the event type according to the acquired event type identifier of the current event. The event types include: an add file event, an add folder event, a delete file event, a delete folder event, and a file content change event.
Step S202, when the event type is a file adding event or a folder adding event, determining an event subtype based on file information, wherein the event subtype comprises a renaming event or a moving event;
step S203, when the event type is a file deletion event or a folder deletion event, judging whether a task queue contains a task of the path information of the current event, and determining the event subtype.
Step S204, when the event type is a file content change event, marking the event as a modification event, searching the file information in the sqlite3 according to the path information of the event, if the event is found, storing the modified time information, and putting the current event into a task queue; if not, the modified file information is saved, and the current event is put into a task queue. Specifically, for an event with changed content, the path information and the system information ino corresponding to the event are not changed, and the modification time information is changed, so that the file information of the event is searched in sqlite3 according to the path information, the time information in the file information is modified and stored, if the file information of the event is not found in sqlite3 according to the path information, which indicates that the storage has not been performed or the storage has failed, the modified file information (the event type identifier, the path information, the modified time information, and the system information ino) is directly stored, and the current event is placed in a task queue.
In summary, in the file monitoring method provided in the embodiment of the present invention, the event type is determined according to the obtained file information of the current event; when the event type is a file adding event or a folder adding event, determining an event subtype based on file information; when the event type is a file deleting event or a folder deleting event, judging whether a task queue contains a task of the path information of the current event or not, and determining the event subtype. The method and the device solve the problems that in the prior art, nodes are used for monitoring file changes from fs.watch and fs.watch File, the monitoring effect is inaccurate, and multiple times of triggering can be realized, and renaming and mobile events can be monitored.
Referring to fig. 3 and fig. 4, which are flowcharts illustrating steps of adding a file event and adding a folder event in a file listening method according to an embodiment of the present invention, the file listening method includes:
based on the file information, determining event subtypes as:
based on the system information ino, searching and judging whether the system information ino same as the system information ino exists in a sqlite3 database;
if the same system information ino exists in the sqlite3 database, judging whether the path information is consistent;
if the path information is inconsistent, marking the path information as a renaming event or a moving event, and modifying the path information of the sqlite3 database to obtain modified path information;
judging whether the parent directories are consistent;
and if the parent directory is consistent, the current event and the modified path information are put into a task queue and marked as a renaming event.
And if the parent directories are not consistent, the current event and the modified path information are put into a task queue and marked as a mobile event.
Referring to fig. 3 and fig. 4, which are flowcharts illustrating steps of a file listening method according to an embodiment of the present invention, the file listening method includes:
if the same system information ino does not exist in the sqlite3 database, or the same system information ino exists in the sqlite3 database and the path information is consistent, the current event is marked as a file adding event, the path information, the modification time information and the system information ino value of the current event are modified, the modified file information is stored in the sqlite3 database, and the current event and the modified file information are placed in a task queue.
Referring to fig. 4, a flowchart illustrating steps of a file listening method according to an embodiment of the present invention is shown, where the file listening method includes: when the event type is an event of adding a folder, if the parent directory is consistent, the current event and the modified path information are put into a task queue, and after the event is marked as a renamed event, or if the parent directory is inconsistent, the current event and the modified path information are put into the task queue, and after the event is marked as a mobile event, the method further comprises the following steps:
checking whether the deleted folder array deleteArr contains the path information before modification;
if the path information before modification exists, deleting the corresponding data in the deleteArr;
and if the path information before modification does not exist, no operation is needed, and the next event is waited.
Referring to fig. 5 and fig. 6, which are flowcharts illustrating steps of deleting a file event or deleting a folder event of a file monitoring method according to an embodiment of the present invention, the file monitoring method determines whether a task queue contains a task of path information of the current event, and determines an event subtype as follows:
judging whether a task queue contains a task of the path information;
if the task queue contains the tasks of the path information, judging whether the task queue is a file adding event or a folder adding event according to the event type identifier;
if the event is a file adding event or a folder adding event, the event is marked as a renaming event or a moving event;
if the task queue does not contain the task of the path information, or if the task queue contains the task of the path information but does not add a file event, marking the current event as a deletion event, deleting the path information in the sqlite3 database, and putting the current event into the task queue;
if the task queue contains the task of the path information but not the folder adding event, clearing the delayed execution setTimeout of the periodical, marking the current event as a folder deleting event, putting the current event into a folder deleting array deleteArr, and after creating the timer and delaying the execution setTimeout for 500ms, executing the following steps: traversing a delete folder array deleteArrr, marking the current event as a delete folder event, deleting the path information of the current event in the sqlite3 database, putting the current event into a task queue, and marking the current event as a delete folder event.
Referring to fig. 8, a structural framework diagram of a file monitoring device according to still another embodiment of the present invention is shown, where the file monitoring device includes:
a first determining module 110, configured to determine an event type according to the obtained file information of the current event; the file information includes: event type identification, system information ino, path information and father directory information;
a second determining module 120 for determining an event subtype based on the file information when the event type is an add file event or an add folder event, the event subtype including a rename event or a move event;
the third determining module 130 is configured to, when the event type is a delete file event or a delete folder event, determine whether the task queue includes a task of the path information of the current event, and determine an event subtype.
A fourth determining module 140, configured to mark the event as a modification event when the event type is a file content change event, search for file information in the sqlite3 according to path information of the event, if the file information is found, save modified time information, and place the current event in a task queue; if not, the modified file information is saved, and the current event is put into a task queue. Specifically, for an event with changed content, the path information and the system information ino corresponding to the event are not changed, and the modification time information is changed, so that the file information of the event is searched in sqlite3 according to the path information, the time information in the file information is modified and stored, if the file information of the event is not found in sqlite3 according to the path information, which indicates that the storage has not been performed or the storage has failed, the modified file information (the event type identifier, the path information, the modified time information, and the system information ino) is directly stored, and the current event is placed in a task queue.
In summary, the file monitoring apparatus provided in the embodiment of the present invention determines the event type according to the obtained file information of the event; when the event type is a file adding event or a folder adding event, determining an event subtype based on file information; when the event type is a file deleting event or a folder deleting event, judging whether a task queue contains a task of the path information of the current event or not, and determining the event subtype. The method and the device solve the problems that in the prior art, nodes are used for monitoring file changes from fs.watch and fs.watch File, the monitoring effect is inaccurate, and multiple times of triggering can be realized, and renaming and mobile events can be monitored.
Optionally, the second determining module 120 is configured to:
based on the system information ino, searching and judging whether the system information ino same as the system information ino exists in a sqlite3 database;
if the same system information ino exists in the sqlite3 database, judging whether the path information is consistent;
if the path information is inconsistent, marking the path information as a renaming event or a moving event, and modifying the path information of the sqlite3 database to obtain modified path information;
judging whether the parent directories are consistent;
if the parent directory is consistent, the current event and the modified path information are put into a task queue and marked as a rename event;
and if the parent directories are not consistent, the current event and the modified path information are put into a task queue and marked as a mobile event.
Optionally, the second determining module 120 is further configured to:
if the same system information ino does not exist in the sqlite3 database, or if the same system information ino exists in the sqlite3 database and the path information is consistent, the system information is marked as an added file event, the path information, the modification time information and the system information ino value of the current event are modified, the modified file information (including the path information, the modification time information and the system information ino value) is stored in the sqlite3 database, and the current event and the modified file information are placed in a task queue.
As shown in fig. 9, optionally, when the event type is an add folder event, if the parent directory is consistent, the current event and the modified path information are placed in a task queue, and after the event is marked as a rename event, or if the parent directory is inconsistent, the current event and the modified path information are placed in a task queue, and after the event is marked as a move event, the second determining module 120 further includes a deleting module 1120 configured to:
checking whether the deleted folder array deleteArr contains the path information before modification;
if the path information before modification exists, deleting the corresponding data in the deleteArr;
and if the path information before modification does not exist, no operation is needed, and the next event is waited.
Optionally, the third determining module 130 is configured to:
judging whether a task queue contains a task of the path information;
if the task queue contains the tasks of the path information, judging whether the task queue is a file adding event or a folder adding event according to the event type identifier;
if the file event is added or the folder event is added, the event is marked as a renaming event or a moving event.
And if the task queue does not contain the task of the path information or if the task queue contains the task of the path information but not the file adding event, marking the task queue as a deleting event, deleting the path information in the sqlite3 database, and putting the task queue into a task queue.
If the task queue contains the task of the path information but not the folder adding event, clearing the delayed execution setTimeout of the timer, marking the current event as a folder deleting event, putting the current event into a folder deleting array deleteArr, and executing the following steps after the timer is created and the setTimeout is delayed for 500 ms: traversing a delete folder array deleteAddr, marking the current event as a delete event, deleting the path information of the current event in the sqlite3 database, deleting the sqlite3 database, putting the current event into a task queue, and marking the current event as a delete folder event.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explaining the principles of the invention and are not to be construed as limiting the invention. Therefore, any modification, equivalent replacement, improvement and the like made without departing from the spirit and scope of the present invention should be included in the protection scope of the present invention. Further, it is intended that the appended claims cover all such variations and modifications as fall within the scope and boundaries of the appended claims or the equivalents of such scope and boundaries.
Claims (10)
1. A file listening method is characterized by comprising the following steps:
determining the event type according to the obtained file information of the current event; the file information includes: event type identification, system information ino, path information, modification time information and father directory information;
when the event type is a file adding event or a folder adding event, determining an event subtype based on file information, wherein the event subtype comprises a renaming event or a moving event;
when the event type is a file deleting event or a folder deleting event, judging whether a task queue contains a task of the path information of the current event or not, and determining the event subtype.
2. The method according to claim 1, characterized in that, based on the file information, the event subtype is determined to be in particular:
based on the system information ino, searching and judging whether the system information ino same as the system information ino exists in a sqlite3 database;
if the same system information ino exists in the sqlite3 database, judging whether the path information is consistent;
if the path information is not consistent, marking the current event as a rename event or a mobile event, and modifying the path information of the sqlite3 database to obtain modified path information;
judging whether the parent directories are consistent;
if the parent directory is consistent, the current event and the modified path information are put into a task queue and marked as a rename event;
and if the parent directories are not consistent, the current event and the modified path information are put into a task queue and marked as a mobile event.
3. The method of claim 2, wherein if the same system information ino does not exist in the sqlite3 database, or the same system information ino exists in the sqlite3 database and the path information is consistent, the file event is marked as an add file event, the path information, the modification time information and the system information ino value of the current event are modified, the modified file information is saved in the sqlite3 database, and the current event and the modified file information are placed in a task queue.
4. The method of claim 2, wherein when the event type is an add folder event, if the parent directory is consistent, the current event and the modified path information are placed in a task queue, and after the event is marked as a rename event, or if the parent directory is inconsistent, the current event and the modified path information are placed in a task queue, and after the event is marked as a move event, the method further comprises:
checking whether the deleetarr array of the deleted folder contains the path information before modification of the current event;
if the path information before modification exists, deleting the corresponding data in the deleteArr;
and if the path information before modification does not exist, no operation is needed, and the next event is waited.
5. The method according to claim 1, wherein whether a task queue contains a task of the path information of the current event is determined, and the event subtype is determined as follows:
judging whether a task queue contains a task of the path information;
if the task queue contains the tasks of the path information, judging whether the task queue is a file adding event or a folder adding event according to the event type identifier;
if the file event or the folder event is added, marking the file event or the folder event as a rename event or a move event;
if the task queue does not contain the task of the path information, or if the task queue contains the task of the path information but does not add a file event, marking the current event as a deletion event, deleting the path information in the sqlite3 database, and putting the path information into the task queue;
if the task queue contains the tasks of the path information but not the folder adding event, marking the current event as a folder deleting event, and putting the current event into a folder deleting array deleteArr;
traversing a delete folder array deleteArr, marking the current event as a delete event, deleting the path information of the current event in the sqlite3 database, putting the current event into a task queue, and marking the current event as a delete folder event.
6. A file listening device, comprising:
the first determining module is used for determining the event type according to the obtained file information of the current event; the file information includes: event type identification, system information ino, path information, modification time information and father directory information;
the second determination module is used for determining an event subtype based on the file information when the event type is a file adding event or a folder adding event, wherein the event subtype comprises a renaming event or a moving event;
and the third determining module is used for judging whether the task queue contains the task of the path information of the current event or not and determining the event subtype when the event type is a file deleting event or a folder deleting event.
7. The apparatus of claim 6, wherein the second determining module is configured to:
based on the system information ino, searching and judging whether the system information ino same as the system information ino exists in a sqlite3 database;
if the same system information ino exists in the sqlite3 database, judging whether the path information is consistent;
if the path information is inconsistent, marking the path information as a renaming event or a moving event, and modifying the path information of the sqlite3 database to obtain modified path information;
judging whether the parent directories are consistent;
if the parent directory is consistent, the current event and the modified path information are put into a task queue and marked as a rename event;
and if the parent directories are not consistent, the current event and the modified path information are put into a task queue and marked as a mobile event.
8. The apparatus of claim 7, wherein the second determining module is further configured to:
if the same system information ino does not exist in the sqlite3 database, or if the same system information ino exists in the sqlite3 database and the path information is consistent, the system information is marked as an added file event, the path information, the modification time information and the system information ino value of the current event are modified, the modified file information is stored in the sqlite3 database, and the current event and the modified file information are placed in a task queue.
9. The apparatus of claim 7, wherein when the event type is an add folder event, if the parent directory is consistent, the current event and the modified path information are placed in a task queue, and after the event is marked as a rename event, or if the parent directory is inconsistent, the current event and the modified path information are placed in a task queue, and after the event is marked as a move event, the second determining module further comprises a deleting module configured to:
checking whether the deleted folder array deleteArr contains the path information before modification;
if the path information before modification exists, deleting the corresponding data in the deleteArr;
and if the path information before modification does not exist, no operation is needed, and the next event is waited.
10. The apparatus of claim 6, wherein the third determining module is configured to:
judging whether a task queue contains a task of the path information;
if the task queue contains the tasks of the path information, judging whether the task queue is a file adding event or a folder adding event according to the event type identifier;
if the file event or the folder event is added, marking the file event or the folder event as a rename event or a move event;
if the task queue does not contain the task of the path information, or if the task queue contains the task of the path information but does not add a file event, marking the task queue as a deletion event, deleting the path information in the sqlite3 database, and putting the task queue with the path information;
if the task queue contains the tasks of the path information but not the folder adding event, marking the current event as a folder deleting event, and putting the current event into a folder deleting array deleteArr;
traversing a delete folder array deleteArr, marking the current event as a delete event, deleting the path information of the current event in the sqlite3 database, putting the current event into a task queue, and marking the current event as a delete folder event.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111251303.7A CN113688106B (en) | 2021-10-27 | 2021-10-27 | File monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111251303.7A CN113688106B (en) | 2021-10-27 | 2021-10-27 | File monitoring method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113688106A true CN113688106A (en) | 2021-11-23 |
| CN113688106B CN113688106B (en) | 2022-04-15 |
Family
ID=78588192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111251303.7A Active CN113688106B (en) | 2021-10-27 | 2021-10-27 | File monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113688106B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117009309A (en) * | 2023-05-31 | 2023-11-07 | 合芯科技(苏州)有限公司 | File real-time synchronization method and device based on rsync |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090077136A1 (en) * | 2007-09-18 | 2009-03-19 | Hiromi Igawa | File management system, file management method, and file management program |
| US8370341B1 (en) * | 2012-01-06 | 2013-02-05 | Inkling Systems, Inc. | Systems and methods for determining and facilitating content updates for a user device |
| CN102930218A (en) * | 2012-10-23 | 2013-02-13 | 深圳市汇智集信息科技有限公司 | File management system and file management method |
| CN103198100A (en) * | 2013-03-13 | 2013-07-10 | 中国科学院计算技术研究所 | Renaming method and renaming system for file synchronization among multiple devices |
| CN103699846A (en) * | 2013-12-25 | 2014-04-02 | 浪潮(北京)电子信息产业有限公司 | Method and device for intercepting changed files in LINUX system |
| CN104133544A (en) * | 2013-08-26 | 2014-11-05 | 腾讯科技（深圳）有限公司 | File processing method, device and terminal |
| CN104636437A (en) * | 2014-12-31 | 2015-05-20 | 华为技术有限公司 | Event notification method and device and monitor processing method |
| CN106612376A (en) * | 2016-12-27 | 2017-05-03 | 努比亚技术有限公司 | Mobile terminal and file processing method thereof |
| CN107645546A (en) * | 2017-09-12 | 2018-01-30 | 深圳Tcl新技术有限公司 | File monitor method, smart machine and storage medium based on Android system |
| CN109040080A (en) * | 2018-08-10 | 2018-12-18 | 中央电视台 | File distorts processing method, device, cloud service platform and storage medium |
-
2021
- 2021-10-27 CN CN202111251303.7A patent/CN113688106B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090077136A1 (en) * | 2007-09-18 | 2009-03-19 | Hiromi Igawa | File management system, file management method, and file management program |
| US8370341B1 (en) * | 2012-01-06 | 2013-02-05 | Inkling Systems, Inc. | Systems and methods for determining and facilitating content updates for a user device |
| CN102930218A (en) * | 2012-10-23 | 2013-02-13 | 深圳市汇智集信息科技有限公司 | File management system and file management method |
| CN103198100A (en) * | 2013-03-13 | 2013-07-10 | 中国科学院计算技术研究所 | Renaming method and renaming system for file synchronization among multiple devices |
| CN104133544A (en) * | 2013-08-26 | 2014-11-05 | 腾讯科技（深圳）有限公司 | File processing method, device and terminal |
| CN103699846A (en) * | 2013-12-25 | 2014-04-02 | 浪潮(北京)电子信息产业有限公司 | Method and device for intercepting changed files in LINUX system |
| CN104636437A (en) * | 2014-12-31 | 2015-05-20 | 华为技术有限公司 | Event notification method and device and monitor processing method |
| CN106612376A (en) * | 2016-12-27 | 2017-05-03 | 努比亚技术有限公司 | Mobile terminal and file processing method thereof |
| CN107645546A (en) * | 2017-09-12 | 2018-01-30 | 深圳Tcl新技术有限公司 | File monitor method, smart machine and storage medium based on Android system |
| CN109040080A (en) * | 2018-08-10 | 2018-12-18 | 中央电视台 | File distorts processing method, device, cloud service platform and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| SMALLZIP: "Node、node-watch、Chokidar实现文件监听封装思路解析", 《简书》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117009309A (en) * | 2023-05-31 | 2023-11-07 | 合芯科技(苏州)有限公司 | File real-time synchronization method and device based on rsync |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113688106B (en) | 2022-04-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11082489B2 (en) | Method and system for displaying similar email messages based on message contents | |
| US9645892B1 (en) | Recording file events in change logs while incrementally backing up file systems | |
| US10198452B2 (en) | Document tracking for safe save operations | |
| US10394758B2 (en) | File deletion detection in key value databases for virtual backups | |
| US11093340B2 (en) | Summary file change log for faster forever incremental backup | |
| CN108021590B (en) | Target object attribute determining method, attribute updating method and device | |
| US10204016B1 (en) | Incrementally backing up file system hard links based on change logs | |
| WO2007068600B1 (en) | Generating backup sets to a specific point in time | |
| CN102360410B (en) | User operation discovery method of file system and synchronous system utilizing the same | |
| CN103577567A (en) | Method for uninstalling application and deleting garbage file in Android system | |
| CN106354884B (en) | Data object deleting method and device based on distributed file system | |
| CN111198856B (en) | File management method, device, computer equipment and storage medium | |
| CN107040576B (en) | Information pushing method and device and communication system | |
| US20200233837A1 (en) | Intelligent method to index storage system files accounting for snapshots | |
| US11593491B2 (en) | Identifying a software vulnerability | |
| US20140310324A1 (en) | Systems and methods for automatically sorting and indexing electronic files | |
| CN113688106B (en) | File monitoring method and device | |
| US8843450B1 (en) | Write capable exchange granular level recoveries | |
| CN114968966A (en) | Distributed metadata remote asynchronous replication method, device and equipment | |
| CN107632926B (en) | Service quantity statistical method, device, equipment and computer readable storage medium | |
| US20210034709A1 (en) | Optimizing incremental backups | |
| WO2020151241A1 (en) | Information non-trace exposure collection method and device | |
| CN113868194B (en) | Management method, device, system and medium for local user group of storage equipment | |
| CN111625500B (en) | File snapshot method and device, electronic equipment and storage medium | |
| US9158632B1 (en) | Efficient file browsing using key value databases for virtual backups |
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 |