Re: Waiting for a file to be written

I'm pretty sure that the problem isn't that my_file.txt isn't fully written when you call system, but rather that it's modified by the next iteration of the parent script before the child script reads it fully.

The solution is to either use locking, or not to spawn the child script in the background.

(If you want to learn more about locking Super Search for it, we had many discussion about that).

Comment on Re: Waiting for a file to be written Download Code

Replies are listed 'Best First'.
Re^2: Waiting for a file to be written by why_bird (Pilgrim) on Oct 14, 2008 at 13:56 UTC
Yes, of course you are right, according to my own output! Thanks for the correction, and suggestions :) I need to run the child processes in the background (it's a series of long jobs controlled by a queue manager) so I will look into locking. sleep(10) works too, though it's a rough hack... ........ Those are my principles. If you don't like them I have others. -- Groucho Marx .......	[reply]
Re^3: Waiting for a file to be written by SuicideJunkie (Vicar) on Oct 14, 2008 at 16:33 UTC
Trivial 2-party locking mechanism: Why not have the child delete the file when it is finished with it? The parent can then wait for the file to disappear before creating the next version of it.	[reply]
Re^4: Waiting for a file to be written by jfroebe (Parson) on Oct 14, 2008 at 20:51 UTC
Another option would be to use Linux::Inotify2 if the operating system is Linux. The trigger would be on IN_CLOSE_WRITE "writable fd to file / to object was closed". :) Jason L. Froebe Blog, Tech Blog	[reply]