Anyone ever seen this? The file is hosted on a Solaris box, and is accessed over a SAMBA mount. The developer makes changes via the app and saves the file, then he goes to the Solaris machine and compiles the package. The first compile completes without any message. Then he makes a second change via the app, goes back to the Solaris machine and compiles the package, and it gives him this message about the file being temporarily unavailable, then after five or ten seconds it compiles fine.
Not a big problem.
My guess would be that it's related to accessing the file over SAMBA. Just curious if there's something I can tweak to make it run a little smoother.
Thanks!
Not a big problem.
My guess would be that it's related to accessing the file over SAMBA. Just curious if there's something I can tweak to make it run a little smoother.
Thanks!