• Home
Name Date Size #Lines LOC

..--

.gitignoreD03-May-2024132 1312

MakefileD03-May-2024257 105

READMED03-May-20241.2 KiB3936

inotify.hD03-May-20241.7 KiB6846

inotify01.cD03-May-20243.6 KiB172121

inotify02.cD03-May-20245.4 KiB230174

inotify03.cD03-May-20243.9 KiB180130

inotify04.cD03-May-20244.3 KiB176118

inotify05.cD03-May-20243.3 KiB160117

inotify06.cD03-May-20242.7 KiB12880

inotify07.cD03-May-20245 KiB193135

inotify08.cD03-May-20244.7 KiB187125

inotify09.cD03-May-20242.4 KiB10772

inotify10.cD03-May-20245.7 KiB220166

inotify11.cD03-May-20242.7 KiB13486

inotify12.cD03-May-20243.7 KiB169117

README

1This contains two tests for the inotify subsystem.
2
3The  inotify  API  provides  a mechanism for monitoring file system events. $
4Inotify can be used to monitor individual files, or to monitor directories. $
5When a directory is monitored, inotify will return events for the directory$
6itself, and for files inside  the directory.
7
8The tests are intended to do the following:
9test 1:
10	initialize inotify for the test file
11	generate sequence events:
12		operation			expected event
13		-----------------------------------------
14		chmod file			IN_ATTRIB
15		open read-only			IN_OPEN
16		read				IN_ACCESS
17		close				IN_CLOSE_NOWRITE
18		open read-write			IN_OPEN
19		write				IN_MODIFY
20		close				IN_CLOSE_WRITE
21	check that all events have been received
22test 2:
23	initialize inotify for the test directory
24	generate sequence events:
25		operate				expected event
26		-----------------------------------------
27		chmod				IN_ISDIR | IN_ATTRIB
28		creat file			IN_CREATE
29						IN_OPEN
30		close				IN_CLOSE_WRITE
31		rename file			IN_MOVED_FROM
32						IN_MOVED_TO
33		rename yourself			IN_MOVE_SELF
34		unlink file			IN_DELETE
35		rename yourself again
36		rename back			IN_MOVE_SELF
37	check that all events have been received and the last two successive
38	IN_MOVE_SELF events will be coalesced into a single one.
39