The parl.exe executable is stored on the local users pc. The .par file is
stored on the network drive. Due to security issues, .exe files are not
allowed on the network drive.
The files are being cached on the local users pc under c:\documents and
settings\{user}\local setttings\temp\par-{user}
Thank You
Linn White
"Eadon, Bryant"
<[EMAIL PROTECTED] To: [email protected]
suisse.com> cc:
bcc:
03/30/2006 09:26 AM Subject: RE: Caching
additional files
-----Original Message-----
From: Masood, Rehman [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 30, 2006 9:07 AM
To: [email protected]
Subject: Re: Caching additional files
Unless I am mistaken, there is now way to force the client pcs to refresh
the cache, this would be a manual process. I am sure the gurus will have to
verify that though :)
On 3/30/06, Linn White <[EMAIL PROTECTED]> wrote:
>
> I have a .par file stored on a network drive. All the computers running
> the par file are using the parl.exe executable. The files are cached on
> their pc and everything is working as it should. However, I have
numerous
> additional files packed into the par. When I make changes to these
files,
> recompile the par and place it on the network drive, other user cannot
see
> the updated files, because the old files are being pulled from their
local
> cache. Changes made to my scripts though are reflected. How do I make
> sure the additional files replace the existing chache files?
>
>
> Linn
---------------------
You're having the clients explicitly close the parl.exe file ? They way
any binary works is that it is first grabbed from a storage source (network
drive, hard drive, CD , etc.. ) from there it is loaded into memory and
run. That's a really glossed over version of what happens, as long as they
are completely shutting down all instances of the application then opening
the parl.exe from the network drive should be fine. Caching should only
occur if the application is already running. Your script changes would
apply because the executable imports them as needed and "lets go" of them
from memory when done.
I'm sure you've already checked that you're putting it on the right network
drive ... that would be one of those "D'oh!" moments.
As for the cache .. I'd concur with the manual process : reboot or some
sort of forced refresh. What cache are you talking about btw (and how did
you determine this) ?
Later,
Bryant
==============================================================================
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================
