That seems like a permission problem on the sub directory (or file) such that the file is not viewable or create-able by the user of record (cpit?).
It is more complicated than just allowing cpit account to access /var/run to create a .pid file. Each component of TSCO creates its own .pid file below the BCO_HOME directory:
But the caplan script references a .pid file that never gets created. (see attached file)
SYSV init scripts are not well suited to managing multiple services, the best approach is to create as set of systemd service definitions. I was hoping this had already been done.
caplan 3.6 K
the scrip references /var/run/caplan.pid which is not in the /opt/bmc/BCO/ path. does the user of record have permissions to the /var/run directory?
not exactly on target but the comment on this request seems like what you are looking for
Other mentions of systemd