| Title: | P4DTI may fail if Perforce client exists and is broken |
| Status: | closed |
| Priority: | essential |
| Assigned user: | Nick Barnes |
| Organization: | Ravenbrook |
| Description: | The P4DTI creates a Perforce client when it first runs. The client name is "p4dti-" concatenated with the machine name (as returned by Python's socket.gethostname() function). This Perforce client may already exist, and may have a clientspec which is broken in such a way that it prevents the P4DTI from running, as reported by a customer [1]. |
| Analysis: | The P4DTI should try harder to use a unique Perforce client, without a broken client spec. Maybe it should just fail if the automatically-generated client name already exists (this can be checked by doing "p4 clients", which doesn't need an existing client to run). This is Perforce job 008038.[2] |
| How found: | customer |
| Evidence: | [1] <http://info.ravenbrook.com/mail/2002/05/02/18-59-47/0.txt>[2] < http://info.ravenbrook.com/mail/2002/05/07/18-30-01/0.txt> |
| Observed in: | 1.4.2 |
| Introduced in: | 0.3.0 |
| Created by: | Nick Barnes |
| Created on: | 2002‑05‑03 12:00:20 |
| Last modified by: | Nick Barnes |
| Last modified on: | 2003‑05‑30 17:33:55 |
| History: | 2002-05-02 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 46723 | closed | 2003‑05‑30 17:33:15 | Nick Barnes | Work around broken client spec or depot list. |
Generated at 2013-05-25 09:00:12 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#476 $
Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.