Discussion:
[p4] Getting rid of "dead" workspaces
John G. Lussmyer
15 years ago
Permalink
I had a machine die recently that had some files checked out into it's
workspace.
The new machine has a different name, so P4V won't let me open that
workspace.
All I need to do is to tell Perforce that those files are no longer
checked out, and delete the workspace.

What is the recommended way to do that?
--
--
John G. Lussmyer mailto:***@CasaDelGato.Com
Electric Vehicle Battery Monitoring Systems, http://www.CasaDelGato.com
Matt Janulewicz
15 years ago
Permalink
Since the machine is dead I assume that the physical files on it are
gone and you don't care about them. In that case you can just force
delete the workspace (as an admin) and the checkouts go with it:

p4 client -d -f <clientname>

We have situations here where the client root is on a network share and
a machine goes south. In this case you can re-host the client. Just
change the client's Host to the new machine you want to access it from
and continue working. This ability also comes in handy when a drive
holding a client root is transplanted into a new machine.


-Matt Janulewicz
Lucasfilm Entertainment Company Ltd.
Post by John G. Lussmyer
I had a machine die recently that had some files checked out into it's
workspace.
The new machine has a different name, so P4V won't let me open that
workspace.
All I need to do is to tell Perforce that those files are no longer
checked out, and delete the workspace.
What is the recommended way to do that?
Rick Macdonald
15 years ago
Permalink
I think I have done

p4 -H oldmachine sync -k //workspace/...

Rick
Post by John G. Lussmyer
I had a machine die recently that had some files checked out into it's
workspace.
The new machine has a different name, so P4V won't let me open that
workspace.
All I need to do is to tell Perforce that those files are no longer
checked out, and delete the workspace.
What is the recommended way to do that?
Rick Macdonald
15 years ago
Permalink
Silly me, of course I meant p4 revert -k, not sync!

Rick
...
Stuart Yusem
15 years ago
Permalink
Hi John,
I think that you may find an easy fix - edit the p4 client and remove the line that says:

Host: HereIsTheMachineName

Then that client can be used on any machine.


You could then use that client this way:

export P4CLIENT=someClientName

# Close any open files
$ p4 revert //...


And you should be able to delete it this way:

$ p4 client -fd someClientName
Client someClientName deleted.


And here is the page in the Perforce Command Reference - for that detail:

http://www.perforce.com/perforce/doc.current/manuals/cmdref/client.html


Note that the Host: field is optional


I hope this helps you.

Stuart

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| Stuart Yusem Work: 408-822-4603 |
| Perforce Administrator ***@netapp.com |
| Email: ***@yahoo.com Cell: 408-857-5830 |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
I had a machine die recently that had some files checked out into it's workspace.
The new machine has a different name, so P4V won't let me open that workspace.
All I need to do is to tell Perforce that those files are no longer checked out, and delete the workspace.
What is the recommended way to do that?
--
Electric Vehicle Battery Monitoring Systems, http://www.CasaDelGato.com
_______________________________________________
http://maillist.perforce.com/mailman/listinfo/perforce-user
Continue reading on narkive:
Loading...