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

Olle Hallin olle.hallin at gmail.com
Thu Sep 20 07:46:01 PDT 2007


Simple solution: Remove the hostname from the workspace definition. It's
just there for protection against
using the wrong workspace in the wrong box.

HTH
Olle


2007/9/20, Gabor Maghera <gmaghera at gmail.com>:
>
> 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
>



-- 
Olle Hallin M.Sc.
+46 70 6653071
olle.hallin at hit.se
www.hit.se


More information about the perforce-user mailing list