Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't read events from /dev/bus #197

Closed
Nhoya opened this issue Feb 7, 2017 · 1 comment
Closed

Can't read events from /dev/bus #197

Nhoya opened this issue Feb 7, 2017 · 1 comment
Labels

Comments

@Nhoya
Copy link

Nhoya commented Feb 7, 2017

Before reporting an issue, please ensure you are using the latest release of fsnotify.

Which operating system (GOOS) and version are you using?

Linux: Debian Jessie 8.7

Please describe the issue that occurred.

adding a watcher on /dev/bus i'm unable to read events from it, otherwise inotify can

Inotify output

inotifywait -mr -e create -e delete /dev/bus
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/dev/bus/usb/003/ DELETE 069
/dev/bus/usb/003/ CREATE 070
@Nhoya Nhoya changed the title Can't read events from /dev/dbus Can't read events from /dev/bus Feb 7, 2017
@arp242 arp242 added the bug label Jul 29, 2022
@arp242
Copy link
Member

arp242 commented Jul 30, 2022

You set up the watcher on /dev/bus, but the path that gets modified is /dev/bus/usb/003/. Your inotifywait command has -r for recursive watches, but this isn't supported in fsnotify (yet, WIP in #472).

If I use fsnotify /dev/bus/usb I get the same events as inotifywait if I plug in and unplug an USB drive.

Closing as it's not really related to watching /dev or /dev/bus, but due to the lack of a recursive watcher (#18, #472).

@arp242 arp242 closed this as completed Jul 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants