Jump to content


Member Since 12 Sep 2016
Offline Last Active Today, 02:07 PM

Posts I've Made

In Topic: When does p4 client 'Access' time get updated?

10 October 2019 - 01:38 AM

When I implemented similar cleanup logic for the Public Depot many years ago, I ended up basing it on the user (with "registered" users being automatically exempted from cleanup operations and everyone else getting something like a 1-year grace period), and I just deleted the clients along with the user that owned them, leaving it up to active users to manage their own clients.  Precisely because figuring out how/if someone's "using" a client is so fuzzy, and improperly deleting a client is fairly destructive.

In Topic: When does p4 client 'Access' time get updated?

08 October 2019 - 03:13 AM

View PostMatt Janulewicz, on 07 October 2019 - 11:56 PM, said:

Do "p4 client -t" and "p4 client -o" really only operate on metadata? That doesn't seem right, as those use/display the actual spec, which would insinuate accessing the library file for the spec.

The spec is generated from the metadata, specifically the db.domain and db.view tables.  One db.view entry per View or ChangeView line, and everything else is packed into one db.domain entry.  

There is no "library file" for a spec unless you have a spec depot, and if you do have a spec depot the "source of truth" is still the database (the spec depot is solely used as a backup during write operations).

In Topic: Child Import Overrides

07 October 2019 - 03:45 PM

Have you checked out the component-based development tools that got linked from that thread?  I think that's the "official" solution.

In Topic: Move Perforce server to another HDD

07 October 2019 - 02:19 PM

Are you trying to move just your depot, or the entire server instance?  The steps are different for those two things.

To move just a depot:
1) Don't change P4ROOT.
2) Change the Map.
3) Move just the depot folder to where you set the Map.

To move the entire server instance:
1) Don't change the Map.
2) Change P4ROOT.
3) Move the entire P4ROOT folder (including any depot folders under it) to where you set P4ROOT.

The golden rule in both cases is "move the folder to the place where you said the folder is going to be".  Simple, right?  If you change P4ROOT to "D:\foo" and you leave it at "C:\bar", or you move it but you don't change P4ROOT, the server won't be able to find it any more.  This is not a problem that you can solve by changing things randomly; you need to make those two things match exactly.

If you could elaborate on your "nothing is working", someone could probably help you fix the problem.  Since the way to put things right is to make the things you did match up with each other, fixing it requires knowing what you did and which doesn't match the other.

Some things I would ask for if I were trying to debug this would be:
1) What were you trying to do: move the whole server, or just move one depot?
2) What sort of errors are you getting?
3) What folders did you move where, EXACTLY?  Where is the folder with your db.* files (the server root)?  Where is the folder with your ,v files (the depot)?
4) What does "p4 info" show the server root as?

In Topic: Child Import Overrides

07 October 2019 - 02:14 PM

Check out an earlier thread on this topic: https://forums.perfo...rt-inheritance/

I think the solution that the other poster came up with of making everything a mainline is pretty good -- the current stream inheritance rules aren't set up well to handle this use case, unfortunately.