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

[G Barthelemy]

You could try and make your clients "host-agnostic", simply by
removing the Host: line in the client spec. We often do that with our
Unix clients because they live on automounted home directories and can
be accessed from whatever host the user happen to be logged on (and in
a clustered / grid environment, the host name can change from session
to session).

Guillaume

On 9/19/07, Gabor Maghera <gmaghera at gmail.com> wrote:
> 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).
>
> Many thanks,
> Gabor
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>