One alternative is to use a semaphore file. Have the NT app create a file
named, say busy, just prior to starting the transfer of the big file.
Once the big file is transferred the NT box erases busy. The shell script
would be written so that if the busy file exists, it doesn't touch the
And if you can't do that, just have the script checksum the file every 5
secs, and if it hasn't changed for 10 secs, you're probably set.
Use the suggestion from Rick first though.
Since the W2k client users just copy the relvant files using drag'n'drop
something like a semaphore file
On Mon, May 07, 2001 at 10:27:06AM +0200, Emil Pedersen wrote:
And if you can't do that, just have the script checksum the file every 5
secs, and if it hasn't changed for 10 secs, you're probably set.
Use the suggestion from Rick first though.
Since the W2k client users just copy
On Sat, May 05, 2001 at 08:25:09PM -0700, Rick Commo wrote:
Given that a W2k client copies a large file into a samba share on a
Linux server, how can a process (e.g. shell script) that will read this
file wait until the file is totally transfered?
.
.
.
One alternative is to use a
Given that a W2k client copies a large file into a samba share on a
Linux server, how can a process (e.g. shell script) that will read this
file wait until the file is totally transfered?
The problem is that the file is (on the server) accessible for reading
from the moment the client starts to
on Fri, May 04, 2001 at 03:31:21PM +0200, Alexander Steinert ([EMAIL
PROTECTED]) wrote:
Given that a W2k client copies a large file into a samba share on a
Linux server, how can a process (e.g. shell script) that will read this
file wait until the file is totally transfered?
The problem is
Given that a W2k client copies a large file into a samba share on a
Linux server, how can a process (e.g. shell script) that will read this
file wait until the file is totally transfered?
.
.
.
One alternative is to use a semaphore file. Have the NT app create a file
named, say busy, just
7 matches
Mail list logo
