Donna Garverick wrote:
>
> Dave Waroff wrote:
>
> > I've seen these techniques used:
> >
> > 1) have a daemon wake up every so often and process files
> > in a given directory.
> >
> > 2) schedule a cron job for every so often and process files
> > in a given directory
>
> i believe both of these have been discussed on the list before.....and both
> have a potential problem.  *if* the file is curently being transferred (that
> is, only partially present) when <whatever> grabs it, you're likely to have
> a mess on your hands.
>
> a possible solution might be to watch the file's size.  if it's not changed
> in N minutes, then grab it.
>

You can send a "flag" file after the data file.
Test on the existance of the "flag" file to determine if the
data file is safe to process.
After processing is complete, remove the data file then the
flag file.


Richard
--
Richard L Gambrell, Director of Computing Systems and Networks
Information Technology Division, University of Tennessee at Chattanooga
Fax: 423-425-4150                Support Help-Desk: 423-425-4000
Direct phone: 423-425-5316       ITD Business Office: 423-425-1755
Mobile (urgent): 423-432-5122    Main UTC: 423-425-4111
Email: [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *