OT: using pscp to *move* files

[Bill Akers]

Mike Schwartz wrote:

>>Bill Akers said:
>>
>>I simply set up a batch file on the windows 2000 computer and used the
>>move command to "move" the files to a directory on that computer.
>>Syntax
>>such as: "move /y \\192.168.0.249\share\*.ext C:\movedir". This also
>>    
>>
>
>  Does this ever cause the Windows machine to lock up (or appear to be
>locked up to the end user)?  Does it ever catch a partially written .ext
>file?
>  
>
Never have I had either of those to happen.  We do generate a large 
number of small(100k or less file size) files. I actually can not tell 
you whether there is some kind of locking mechanism at work that 
prevents the  situation you envision from happening with large files. At 
the time that I originally set this up my time to test such things was 
non-existent and since there has been no problem since then I just never 
looked at it again.

>  Years ago I had problems trying to do this, but I was generating fairly
>large sales reports and production schedules on much slower Unix boxes than
>we have available today.
>
>  I finally had to cron the sales jobs to run on the hour, and then schedule
>the MOVE command to trigger on the 1/2 hour in order to insure that that the
>MOVE command didn't try to pick up a partially written .CSV file and cause
>problems.
>  
>
I could envision that happening with quite large files, several 
megabytes, perhaps. I would assume that the currently available 
communication technology between Visionfs/Samba and Windows computers 
would most likely cause the Windows computer to just sit and wait until 
the write was completed.. As you say above the much faster hardware 
today would remove some of that problem. Sounds like you have a solution 
to the problem anyway.

>Mike Schwartz
>
>
>
>_______________________________________________
>Filepro-list mailing list
>Filepro-list at lists.celestial.com
>http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>  
>