| Title | The p4 client is not on path when running from RPM install |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | When running the P4DTI with the startup script from an RPM install (/etc/rc.d/init.d/p4dti start), p4 is not on the path so the P4DTI fails (because the distributed config.py has p4_client_executable just set to "p4"). |
| Analysis | The startup script should make sure (within reason) that the path includes whatever normal bin directory holds p4.
In fact sourcing the useless /etc/rc.d/init.d/functions script kills our PATH. |
| How found | manual_test |
| Evidence | Testing 1.0.2 with some different config files. |
| Observed in | 1.0.2 |
| Introduced in | 1.0.0 |
| Created by | Nick Barnes |
| Created on | 2001-03-05 13:25:42 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:29:59 |
| History | 2001-03-05 NB Created. |