|
> > What does it exactly mean? The IFS is busy? That would be a bit soon > for my taste; a tester just runs some scripts on just 3 PCs that FTP > files to the system, about 2.000 files in total at the moment, size of > about 3KB, containing 5 messages each, so we have 2.000 files with a > total data of 6MB that have to be copied and 10.000 files that have to > be splitted out of these 2.000. And in the process of that we do > receive 3029 for the OPEN (no matter WRITE/READ) either 0 times, 1 > times or 2 times. > (quoting from the manual) [EBUSY] Resource busy. An attempt was made to use a system resource that is not available at this time. The open sharing mode may conflict with another open of this file, or O_WRONLY or O_RDWR is specified and the file is checked out by another user. My guess is that it's just a timing problem. Your process is trying to open a file for read/write when an existing process already has the file open for read/write and hasn't yet closed it. I assume that your system is designed to open the file, read/write that file, and then close it immediately. If so, that's why trying it again a second later solves the problem. It also explains why this happens only rarely. > Did anyone else receive this one? What do you do in your program when > you receive it? My application is an interactive app... it just tells the user about the problem, and the user tries again later. > > Just wait a second and try again? (That seems to work all the time). > Or is there something to set, look at or ? In your situation, I think I'd wait a second and try again (or perhaps less than a second) Possibly have it try for 5 seconds, then give up... Good Luck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.