Hello Mark!
> The reasons given in the release notes for 1.2.0 are:
>
> 1. Overlapping working copies.
> 2. Very large numbers of working copies.
>
> In my case, I use fsvs for more than one purpose.
> In this case, I do have one machine
> where I have an external drive to which I commit
> almost all of that machine's filesytems
> on a daily basis as a fast supplement to regular
> backups (and with much faster access to
> yesterdays files; I think of it akin to Vistas's file versioning).
Fine!
Just being curious - which repository fs do you use? BDB or FSFS?
> That machine does have nested working copies with fsvs,
> but by using "ignore" lists,
> there is no overlap in the repository.
Then everything is fine.
> However, for performance, I have put the
> (single) WAA area in a specially created Reiser filesystem.
That shouldn't really matter.
> The statistics here are probably interesting:
>
> Number of working copies: 27
> find $WAA -type d -print | wc -l : 1892845
Again, out of interest:
how many files are there, how many *empty* directories
(yes, I think there's still some bug), and how many
entries do your working copies have?
(The fastest way to get the last value should be
fsvs st -v $WC | wc -l
;-)
> I guess it might be better if each of those working copies had its own WAA
> tree, but
> maybe fsvs will do that automatically now.
With FSVS_CHARS, yes.
And, answering your $SUBJECT, I don't think you need to.
The only reason (currently) would be if you wanted something
like "fsvs wc disconnect" or similar.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2369707
To unsubscribe from this discussion, e-mail:
[[email protected]].
