Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues


P4DTI issue job000638

Title:"p4dti subsystem is locked" message from startup script
Status:open
Priority:optional
Assigned user:Nick Barnes
Organization:Ravenbrook
Description:After installing the P4DTI RPM on Linux, running "/etc/rc.d/init.d/p4dti start" generated the error message "p4dti subsystem is locked" [1]. We cannot reproduce this except by user error, but the RPM packaging could be improved to prevent such an error.
Analysis:This message means that the lock file /var/lock/subsys/p4dti already exists. This file is used by the startup script itself but not otherwise by the P4DTI. Neither Ravenbrook nor Perforce can reproduce this problem except by not stopping the P4DTI properly when uninstalling, or by running the startup script twice. [2]
Uninstalling (rpm -e) should be changed to delete this file if it is present.
How found:customer
Evidence:[1] <http:/​/​info.ravenbrook.com/​mail/​2002/​11/​28/​00-57-42/​0.txt>
[2] <http:/​/​info.ravenbrook.com/​mail/​2002/​12/​17/​19-54-16/​0.txt>
Observed in:1.5.1
Introduced in:1.0.0
Created by:Nick Barnes
Created on:2002‑12‑11 16:46:32
Last modified by:Nick Barnes
Last modified on:2002‑12‑18 12:37:40
History:2002-12-11 NB Created.
2002-12-18 NB Updated following testing of 1.5.3.

Generated at 2013-05-21 09:32:15 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.

Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues