[p4] When a Mac gets a hostname renamed, the user thinks the workspace is "gone" and Perforce is broken.
Michael.Mirman at mathworks.com
Mon Oct 13 17:14:12 PDT 2008
Our users routinely use different hosts accessing the same clients.
Because of that, we prefer not to have the Hosts field in the client spec at all. If you do this, I can't think why it would be a problem if a Mac changed its name.
IOW, instead of changing the Hosts field to the current host name, just remove it.
Michael Mirman Tel: (508) 647-7555
The MathWorks, Inc. FAX: (508) 647-7061
3 Apple Hill Drive, Natick, MA 01760-2098 mailto:mmirman at mathworks.com
> -----Original Message-----
> From: perforce-user-bounces at perforce.com [mailto:perforce-user-
> bounces at perforce.com] On Behalf Of Peter Hecht
> Sent: Monday, October 13, 2008 7:32 PM
> To: Perforce Users
> Subject: [p4] When a Mac gets a hostname renamed, the user thinks the
> workspace is "gone" and Perforce is broken.
> I work with Mac people. They are OK, really! But some how every once and
> awhile a Mac OS X 10.4/5 gets a different host name. When that happens, I
> have to clear out the host field in the P4 client. Once that is done,
> everything is OK. I don't think it is P4V.app that is causing it, it seems
> like a DHCP issue. Yet, it never happens on Windows machines. The users
> think it is Perforce's fault. I don't but my position doesn't matter when
> it stops them from working.
> I guess I will have to write a script to reset the host on Mac clients.
> Any one have any ideas?
> Peter Hecht
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user