[p4] Seeing have list without updating client access time?

[Eric Busto]

I'll look into obliterate, but if that is the only alternative, I may
just troll through the checkpoints when they do get created.  The thing
keeping us from doing checkpoints frequently is the sheer size of our db
files.  The db.have file on our larger instance is 144GB.  We're doing
some things with journals and mirror servers such that we can
confidently restore the db files in case something bad happens, but
obviously we want to checkpoint more often, and having smaller db files
(the whole point of this exercise) would help make that process quicker.

Thanks for the tips everyone, they are much appreciated!

-----Original Message-----
From: David Faison [mailto:dfaison at photon.com] 
Sent: Wednesday, June 28, 2006 11:56 AM
To: Eric Busto
Cc: perforce-user at perforce.com
Subject: RE: [p4] Seeing have list without updating client access time?


Believe it or not, I think the 'obliterate' command gives you what you
want. Just remember, don't use the "-y" option. Without the "-y" you
remain in report mode (which is what you want!!).

	e.g. p4 -c {client} obliterate //{depot_path}/...#have

Kind of like hunting gnats with a bazooka though. The downside (and it's
a big one) is that the obliterate command is pretty demanding on the
server (not as bad as it was prior to 2005.2, but still a pretty big
gun).

Really, almost any alternative would be better than this. How about
biting the bullet and doing more checkpoints? That would probably cause
less discomfort to your users than frequently calling obliterate. 

 David Faison


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
Sent: Tuesday, June 27, 2006 6:12 PM
To: Eric Busto
Cc: perforce-user at perforce.com
Subject: Re: [p4] Seeing have list without updating client access time?

Count the number of db.have lines in your checkpoint for that client. 
It's not necessarily the most up-to-date, but if you're talking about 
old clients, it doesn't matter.

Steve

Eric Busto wrote:
> I'm working on a script, as I'm sure many of you have before, that
> prunes old clients as a first step to shrinking our utterly ginormous
db
> files.  As part of this, I want to be able to estimate space savings
> based on how large the have list is for each old client.
>
> Finding old clients is easy (p4 -Ztag clients), and finding their have
> list is straightforward as well, but not without updating the access
> times of the client.  I search the perforce-user archives, and found a
> few methods, but all of them update the access time of the client.
>
> Methods tried:
> 1) p4 files //... at client-name (this one was supposed to not update
> access times, but the mail was from 2003, so things may have changed
in
> Perforce land)
> 2) p4 -c client have
> 3) p4 -c client files
>
> Does anyone have any other ideas?  I really want to avoid munching a
> checkpoint if possible, since we take them, well, not as frequently as
I
> would like.
>
>
------------------------------------------------------------------------
-----------
> This email message is for the sole use of the intended recipient(s)
and may contain
> confidential information.  Any unauthorized review, use, disclosure or
distribution
> is prohibited.  If you are not the intended recipient, please contact
the sender by
> reply email and destroy all copies of the original message.
>
------------------------------------------------------------------------
-----------
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>   
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user