P4DTI issue job000243

TitleThe p4 client is not on path when running from RPM install
Assigned userNick Barnes
DescriptionWhen 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").
AnalysisThe 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 foundmanual_test
EvidenceTesting 1.0.2 with some different config files.
Observed in1.0.2
Introduced in1.0.0
Created byNick Barnes
Created on2001-03-05 13:25:42
Last modified byGareth Rees
Last modified on2001-12-10 19:29:59
History2001-03-05 NB Created.


Change Effect Date User Description
9513 closed 2001-03-06 14:11:22 Nick Barnes Fix typo in last changelist.
9511 open 2001-03-06 14:07:41 Nick Barnes Stop sourcing RedHat's oh-so-useful "functions" script, which kills the PATH.