21 messages in com.perforce.perforce-user[p4] anyone have a solution for not h...| From | Sent On | Attachments |
|---|---|---|
| Rita Ozanne | 17 Sep 2001 13:32 | |
| David Rehring | 17 Sep 2001 13:59 | |
| Kumar | 17 Sep 2001 14:31 | |
| Steve Cogorno | 17 Sep 2001 14:42 | |
| Kumar Lakshminarayanan | 17 Sep 2001 15:00 | |
| Matthew Rice | 17 Sep 2001 15:05 | |
| Stephen Vance | 17 Sep 2001 16:47 | |
| Stephen Vance | 17 Sep 2001 16:48 | |
| Chuck Karish | 18 Sep 2001 07:03 | |
| Chuck Karish | 18 Sep 2001 07:07 | |
| Gregg G. Wonderly | 18 Sep 2001 07:13 | |
| Jeff A. Bowles | 18 Sep 2001 08:25 | |
| davi...@redspark.com | 18 Sep 2001 08:43 | |
| Gregg G. Wonderly | 18 Sep 2001 12:20 | |
| Chuck Karish | 19 Sep 2001 07:21 | |
| Chuck Karish | 19 Sep 2001 07:25 | |
| Michael Peck | 19 Sep 2001 08:00 | |
| Chuck Karish | 19 Sep 2001 09:23 | |
| Jack Tan | 19 Sep 2001 09:54 | |
| Michael Go | 20 Sep 2001 14:19 | |
| Dave Lewis | 21 Sep 2001 07:02 |
| Subject: | [p4] anyone have a solution for not having p4 client default to system name?![]() |
|---|---|
| From: | Gregg G. Wonderly (gre...@skymaster.c2-tech.com) |
| Date: | 09/18/2001 12:20:14 PM |
| List: | com.perforce.perforce-user |
Windows is typically used by one person per workstation, so this is less of an issue.
Granted. Then how are clients created with the 'system name' bad then? A client represents a physical disk image of files from the depot. A client should never be used on more than one physical disk structure. So, typically, the system name client setting is fine. Can you provide more information?
Is it possible to use p4 in a client on some host other than that which hosts the client? e.g. via nfs or smb?
In newer versions of perforce you can set the ip-address in the client spec to keep that client from being used from different computer systems and thus more likely different physical disk surfaces.
Another option for setting P4CLIENT is wrapper scripts, but I do like the /etc /profile idea - I'd steal it if my engineers worked on unix!
The windows login script mechanism can be used, and also, via remote scripting management, the 'default client' could probably be set using your local practice for selecting client names.
----- gregg at c2-tech.com (C2 Technologies Inc)




