On Mon, Mar 27, 2000 at 02:03:20PM +0530, Differentiated Software Solutions Pvt. Ltd.
wrote:
> I've worked in other environments (like mainframe) where the schedulers
> have lots of features. One of the features which I'm currently
> looking for is, after a file has been completely copied (or created)
> a process should start. The emphasis is on the word completely. For
> eg: If I have a file which is 100 MB, only after all 100 MB has been
> copied should a process be kicked off. Similarly next time the file
> is deleted and recreated this process will be kicked off.
The UNIX philosophy in general is minimalistic. Though the functionality
that you're asking for might be of use in some special circumstances,
it is not useful for general purpose use. The other rule of thumb is:
whatever can be done at user level shall not be done in the kernel.
In the above cases, the process that is creating or deleting the files
should be responsible for notifying your cron job. Registering callbacks
with the kernel and getting the kernel to call back will not be done in
a general purpose kernel.
Given how conservative Linus personally is - he refuses to put a debugger
or debugging code (like asserts to check certain invariants), it is
extremely unlikely that he'll do anything like what you're asking for.
-Arun
-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH
