in reply to Re^4: Any way to determine path being monitored with Win32::ChangeNotify?
in thread Anyway to determine path being monitored with Win32::ChangeNotify?
>touch test02.txt >C:\SCRIPTS\GnuWin32-bis\bin\ls.exe -il test02.txt 12666373953464529 -rw-rw-rw- 1 lt 0 0 2014-11-13 11:26 test02.txt >C:\SCRIPTS\GnuWin32-bis\bin\ln test02.txt link-to-test02.txt >C:\SCRIPTS\GnuWin32-bis\bin\ls.exe -il test02.txt link-to-test02.txt 12666373953464529 -rw-rw-rw- 2 lt 0 0 2014-11-13 11:26 link-to-test02 +.txt 12666373953464529 -rw-rw-rw- 2 lt 0 0 2014-11-13 11:26 test02.txt >echo Perl > test02.txt >cat test02.txt Perl >cat link-to-test02.txt Perl >C:\SCRIPTS\GnuWin32-bis\bin\ls.exe -il test02.txt link-to-test02.txt 12666373953464529 -rw-rw-rw- 2 lt 0 7 2014-11-13 11:28 link-to-test02 +.txt 12666373953464529 -rw-rw-rw- 2 lt 0 7 2014-11-13 11:28 test02.txt >C:\SCRIPTS\GnuWin32-bis\bin\stat -c "%i %N" test02.txt 12666373953464529 `test02.txt' >C:\SCRIPTS\GnuWin32-bis\bin\stat -c "%i %N\n" link-to-test02.txt 12666373953464529 `link-to-test02.txt'
C:\Windows\system32>fsutil file queryfileid c:\SCRIPTS\test02.txt ID del file: 0x002d00000016a8d1 C:\Windows\system32>fsutil file queryfilenamebyid c:\ 0x002d00000016a +8d1 Nome collegamento causale al file: \\?\C:\SCRIPTS\test02.txt #0x002d00000016a8d1 hex is equal to 12666373953464529 dec (the same nu +mber as above!!!)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^6: Any way to determine path being monitored with Win32::ChangeNotify? the mistery of inodes on windows
by soonix (Chancellor) on Nov 13, 2014 at 12:12 UTC | |
|
Re^6: Any way to determine path being monitored with Win32::ChangeNotify? the mistery of inodes on windows
by BrowserUk (Patriarch) on Nov 13, 2014 at 15:07 UTC | |
by Discipulus (Canon) on Nov 13, 2014 at 15:29 UTC | |
by BrowserUk (Patriarch) on Nov 13, 2014 at 16:02 UTC |