[p4] Windows network drive problems
gwhitfield at europe.ea.com
Thu Sep 29 01:48:08 PDT 2005
You can point each depot location using the Map field of P4 depot.
For example, if you have a depot called "Main", by default the map field
To point this elsewhere, just change it to
You will need to do the same for all depots. This does have the slight
administrative overhead that if you make a new depot in the future you
need to remember to edit the map.
We use this approach on our Windows-hosted system to group all depots
under a single folder underneath P4ROOT, which simplifies our various
system activities for backups & replication, and also generally keeps
things generally tidier.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
Sent: 29 September 2005 00:49
To: Joseph Cochran; perforce-user at perforce.com
Subject: Re: [p4] Windows network drive problems
In pointing to the network drive, is it mounted as a drive letter or are
you trying to use UNC?
When you say your depot, do you mean just the archive files or also the
I don't know of any good way to put your depot files separate from your
db.* files on Windows. On Unix, you would just use a symlink, but
Windows shortcuts aren't as transparent. I wouldn't recommend putting
your db.* files on a network share. Some SAN technologies may be fast
enough, but you will see a performance hit generally.
That said, you can use P4ROOT to change the location. Use either "p4 set
-s P4ROOT=X:\" or "p4 set -S Perforce P4ROOT=X:\" depending on the scope
at which you want the definition seen.
At 05:54 PM 9/28/2005, Joseph Cochran wrote:
>We're setting up perforce in a Windows environment, and have hit a
>stumbling block. I've tried a few ways around it, but so far no luck,
>so I thought I'd put it to the list.
>We want to install perforce so that our depot is on a network drive:
>one that's on our separate file server system. Assume for the moment
>that a Windows install is required. If we attempt to make P4ROOT on the
>network drive, the service won't start up (the same install to a local
>drive works fine). We have not been able to find a solution that will
>give us a reparse point to the network drive, either (basically
>replacing the "depot" folder under P4ROOT with a reparse point instead
>of the actual directory)..
>A simple solution to this would be if we can direct perforce to use a
>depot that's not directly beneath P4ROOT in the folder structure.
>I've looked through the docs available online and not had much success
>looking for a way to do that. Is there an environment variable or some
>other method by which we can repoint the depot?
>Thanks for any help, and if this requires any further explanation,
>please let me know!
>perforce-user mailing list - perforce-user at perforce.com
mailto:steve at vance.com
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user