[p4] Perforce Clients Running on Mac OS where Machine Name Changes

Ivey, William william_ivey at bmc.com
Thu Sep 20 08:40:15 PDT 2007


The host entry is not a required field in the client spec,
just delete it and the client will work no matter what the
host name.

-Wm

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Gabor Maghera
Sent: Wednesday, September 19, 2007 5:51 PM
To: Perforce User
Subject: [p4] Perforce Clients Running on Mac OS where Machine Name
Changes

We are about to deploy Perforce in a Mac OS environment and we ran
across an
interesting issue.  My experience with Perforce so far has been limited
to
Windows and Unix - not quite sure how to deal with this one.  I am
hoping
someone else may have run into this issue and be able to help.

Here's the problem:
Our laptops take on a different host name depending on whether you are
connected to the LAN directly or via VPN.  Any workspace created in
Perforce
will not work by default with both configurations, only with the host
name
used at creation, since that is part of the workspace description.
Therefore, the user must change the host name set in the  workspace in
order
to be able to resume work when switching from on- to off-site and vice
versa.

I am going to talk to IT see if there's anything that can be done form
their
end so the host name stays consistent, but I am curious if any of you
have
ideas on how to overcome this.  I have not found a way to give a user
defined name to the machine (as one would do in Windows).



More information about the perforce-user mailing list