Brandon Casci wrote:
> Since then it appears that Vault needs to retrive the ENTIRE repository
> structure at the start of each new session.
>
> Has anyone else had this problem or am I imagning this?
Unlike most of the other cache files, this one can be really large, and
Vault only writes the repository structure file under certain conditions.
When it retrieves the structure on login, it checks to see if there's a
structure already on disk. If there is, the file isn't written at this
time. If there's no file on disk, the structure is written then.
Later, on client exit, the file on disk is checked (again). If the
repository structure in memory is newer than the one on disk (the header
of the disk file is read and compared), the disk file is overwritten.
So if the Vault client is exiting abnormally (killed process) or perhaps
you're using the IDE client and it's exiting abnormally (maybe Visual
Studio isn't letting us logout?), the file may not be written on exit,
but should have been written when it was first retrieved. You can open
the directory with the cache member files and watch for their creation
when Vault runs. If they're never created, I'll try to track down
other possibilities.
--
Shaw Terwilliger <sterwill@xxxxxxxxxxxxxx>
SourceGear LLC
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|