Date: Mon, 27 Aug 2001 19:17:20 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "A. Sinan Unur" <unursinan AT unur DOT com>
cc: djgpp AT delorie DOT com, "A. Sinan Unur" <asu1 AT cornell DOT edu>
Subject: Re: file system change notification
In-Reply-To: <Pine.LNX.4.04.10108271148140.8635-100000@ficus.frogspace.net>
Message-ID: <Pine.SUN.3.91.1010827191424.22538N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 27 Aug 2001, A. Sinan Unur wrote:

> I guess I wasn't clear. I am not interested in plugging into the Windows
> file operations chain. Rather, I am curious about if I can create similar
> functionality by chaining into DOS interrupts even when not running under
> Windows.

DOS doesn't have this functionality at all, AFAIK.  On Windows, you need 
cooperation from Windows to be able to do that.

> I think it is easier to go with the Windows solution and use
> cygwin for this task.

Since Cywgin produces native Win32 apps, you can use it to register a 
callback that will notify you about any change in the filesystem.

> I have a bunch of programs running on different machines generating data
> on a network drive. I wanted a program on a "monitor" computer to watch
> these data files, and process them when they were done.

If those other programs only create the files, you could simply read the 
directory from time to time (with readdir, for example).