line 69: read: read error: 0: Resource temporarily unavailable

[perlun]

Hi,

Thanks for a nice script. As for others, I found this from the SO post you wrote about it.

However, I run into the error listed above, every time I save a file using VS Code. Very annoying. It doesn't kill the script right away, but the next time I make one more change, it dies. I tried now with nano and I got the same problem.

This is on a plain Debian Buster installation. Kernel is 4.19.0-9-amd64, regular ext4 filesystem. inotify-tools package version follows:

Package: inotify-tools
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 82
Maintainer: Dmitry Bogatov <[email protected]>
Architecture: amd64
Multi-Arch: foreign
Version: 3.14-7
Depends: libc6 (>= 2.14), libinotifytools0 (>= 3.11)
Description: command-line programs providing a simple interface to inotify
 inotify-tools is a set of command-line programs for Linux providing a
 simple interface to inotify. These programs can be used to monitor and
 act upon filesystem events. inotify-tools consists of two utilities:
 .
 inotifywait simply blocks for inotify events, making it appropriate
 for use in shell scripts.
 .
 inotifywatch collects filesystem usage statistics and outputs counts
 of each inotify event.
Homepage: https://github.com/rvoicilas/inotify-tools/wiki/

[tartley]

Interesting. Thanks for reporting. I wonder if I can reproduce it?

[perlun]

What kernel version(s) have you been using this successfully with? Something reasonably similar or something completely different? With ext4 or some other filesystem? On bare metal or virtualized hardware?

(I switched to using entr in the meanwhile. Will probably build something on top of .NET FileSystemWatcher in the longer run, to handle the larger scope of (incrementally) building my web project on-demand.)

[tartley]

Hi apologies for the silence. Probably not useful now but yes, I'm on ext4, on bare metal, and have been on latest Ubuntu this whole time, or the Ubuntu-derived Pop!_OS. For example now that is Pop!_OS 22.04, with kernel 6.0.12.

I was not aware of entr, thanks for mentioning it. I am back here because I have some big plans for 'rerun2' - I must evaluate whether things like entr are perhaps a better substitute for my own evolving needs, or if I need to start adding cmdline options to rerun2...