You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hardlink creation is not noticed. Don't know if this is a bug in fsevent/fsevent-sys, or if it's just how the Apple File System Events API works, or if there is some other problem.
Regular file creation, and even deletion of hardlinks are noticed and reported though.
Steps to reproduce:
On an APFS file system on macOS Catalina, create a directory that we will watch. As an example, let's do:
mkdir -p ~/tmp/hello/world/
Create a file somewhere outside of the watched directory structure.
touch ~/tmp/hello/somefile
Use the fsevent crate to watch the directory that we created in step 1 (~/tmp/hello/world/).
Create a regular file in the watched directory.
touch ~/tmp/hello/world/one
Notice that the file creation is picked up as expected.
Create a hardlink inside of the watched directory.
cd~/tmp/hello/world/ && ln ../somefile .
The hardlink creation is not noticed by fsevent.
The text was updated successfully, but these errors were encountered:
Hardlink creation is not noticed. Don't know if this is a bug in fsevent/fsevent-sys, or if it's just how the Apple File System Events API works, or if there is some other problem.
Regular file creation, and even deletion of hardlinks are noticed and reported though.
Steps to reproduce:
On an APFS file system on macOS Catalina, create a directory that we will watch. As an example, let's do:
mkdir -p ~/tmp/hello/world/
Create a file somewhere outside of the watched directory structure.
touch ~/tmp/hello/somefile
Use the fsevent crate to watch the directory that we created in step 1 (
~/tmp/hello/world/
).Create a regular file in the watched directory.
touch ~/tmp/hello/world/one
Notice that the file creation is picked up as expected.
Create a hardlink inside of the watched directory.
The hardlink creation is not noticed by fsevent.
The text was updated successfully, but these errors were encountered: