Re: File Locking

From: Kenny McCormack (gazelle@yin.interaccess.com)
Date: 04/15/03 

From: gazelle@yin.interaccess.com (Kenny McCormack)
Date: Tue, 15 Apr 2003 17:52:01 GMT

In article <9UVma.14$MT3.281@paloalto-snr1.gtei.net>,
Barry Margolin <barry.margolin@level3.com> wrote:
...
>The usual recommendation is to upload the file to a temporary name, and
>then have the client rename it when it's done. That way, the file that the
>script looks for won't exist at all until the upload is complete.

Or to have the sending process create (send) a flag file after finishing
the main file. The receiver then waits for the existence of the flag file
before accessing the main file. This is nominally better than the rename
method.

The problem with either of these methods is usually that they don't have
any control over the actions of the senders - generally due to some
combination of technical and/or social (political) issues.

Relevant Pages

  • Re: File Locking
    ... >then have the client rename it when it's done. ... >script looks for won't exist at all until the upload is complete. ... Or to have the sending process create a flag file after finishing ...
    (comp.unix.solaris)
  • Re: ftp download
    ... How about if we download directory, wait 1 min, download dir again, ... flag file when they're done. ... When they begin an upload, ... if we just happen to download while the customer is ...
    (microsoft.public.fox.programmer.exchange)
  • Re: ftp download
    ... flag file when they're done. ... After finishing their upload, they put it back. ... if we just happen to download while the customer is ... get a partial file ...
    (microsoft.public.fox.programmer.exchange)