How to filter duplicate system messages from fsnotify
php小编百草在这里与大家分享一种有效的方法,即如何从fsnotify过滤重复的系统消息。在日常的开发工作中,我们经常会遇到需要实时监控文件系统变化的场景,而fsnotify正是一个强大的工具。然而,当系统频繁变动时,可能会导致大量的重复消息出现,给我们的工作带来困扰。因此,本文将教您一种简单而实用的过滤重复系统消息的方法,帮助您提高工作效率。
问题内容
我使用“github.com/fsnotify/fsnotify”来监听文件更改,但是我应该如何多次过滤某些消息?
func listener() { watcher, err := fsnotify.newwatcher() if err != nil { log.fatal(err) } defer watcher.close() done := make(chan bool) go func() { for { select { case event, ok := <-watcher.events: if !ok { return } log.println("event:", event.name, event.op) // writing in this way reduces some messages: if event.op&fsnotify.rename == fsnotify.rename { // do ... } else if event.op&fsnotify.create == fsnotify.create { // do ... } else if event.op&fsnotify.write == fsnotify.write { // do ... } else if event.op&fsnotify.remove == fsnotify.remove { // do ... } case _, ok := <-watcher.errors: if !ok { return } } } }() err = watcher.add("e:/.../demo") if err != nil { log.fatal(err) } <-done }
比如write、create事件发生了好几次,我发现官方已经修复了bug,但是好像没有完全解决
2022/12/12 21:00:55 event: e:\...\demo\a.bbb create 2022/12/12 21:00:55 event: e:\...\demo\a.bbb create 2022/12/12 21:00:55 event: e:\...\demo\a.bbb create 2022/12/12 21:01:57 event: e:\...\demo\2.md write 2022/12/12 21:01:57 event: e:\...\demo\2.md write 2022/12/12 21:01:57 event: e:\...\demo\2.md write 2022/12/12 21:01:57 event: e:\...\demo\2.md write 2022/12/12 21:01:57 event: e:\...\demo\2.md write 2022/12/12 21:01:57 event: e:\...\demo\2.md write 2022/12/12 21:01:57 event: e:\...\demo\2.md write
我应该如何过滤消息?
##############################
var syncMap sync.Map go func() { for { select { case event, ok := <-watcher.Events: if !ok { return } fPath := strings.ReplaceAll(event.Name, "\\", "/") pathKey, _ := syncMap.Load(fPath) if pathKey != 1 { // ... syncMap.Store(fPath, 1) go func() { time.Sleep(time.Second * 2) syncMap.Delete(fPath) }() } case _, ok := <-watcher.Errors: if !ok { return } } } }()
解决方法
如果发出事件的库不在您的控制之下,您只能更改处理重复项的方式。 您可以使用 map[string]bool 来跟踪您已经看到/处理的事件,因此修改您的代码可以执行以下操作:
seenMap := make(map[string]bool) go func() { for { select { case event, ok := <-watcher.Events: if !ok { return } log.Println("event:", event.Name, event.Op) _, seen := seenMap[event.Name] if !seen { // Writing in this way reduces some messages: if event.Op&fsnotify.Rename == fsnotify.Rename { // do ... } else if event.Op&fsnotify.Create == fsnotify.Create { // do ... } else if event.Op&fsnotify.Write == fsnotify.Write { // do ... } else if event.Op&fsnotify.Remove == fsnotify.Remove { // do ... } seenMap[event.Name] = true } case _, ok := <-watcher.Errors: if !ok { return } } } }()
The above is the detailed content of How to filter duplicate system messages from fsnotify. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The article discusses managing Go module dependencies via go.mod, covering specification, updates, and conflict resolution. It emphasizes best practices like semantic versioning and regular updates.

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg
