NewsArchive
10-29-2008, 07:37 AM
Does anyone have a foolproof way to test if a file is being accessed or
locked?
What we have been doing is changing the name of the primary EXE, and then
testing to see if the original name is there.
If it is, the rename failed, and the file is locked by some user.
Ok, i know this is a crude way of doing it, but it worked beautifully until
RDP.
It seems that with RDP on some of the newer servers, the EXE's are cached.
Result: after the install, it tells you to reboot the server. And sometimes,
when the server comes back up, all the exe's and dll's that were replaced
during the install process are gone.
So, any ideas? It is vital that everyone is out of the software before the
update run. I just need a viable way to make sure of this.
Thanks,
--Glenn.
locked?
What we have been doing is changing the name of the primary EXE, and then
testing to see if the original name is there.
If it is, the rename failed, and the file is locked by some user.
Ok, i know this is a crude way of doing it, but it worked beautifully until
RDP.
It seems that with RDP on some of the newer servers, the EXE's are cached.
Result: after the install, it tells you to reboot the server. And sometimes,
when the server comes back up, all the exe's and dll's that were replaced
during the install process are gone.
So, any ideas? It is vital that everyone is out of the software before the
update run. I just need a viable way to make sure of this.
Thanks,
--Glenn.