projects/perforce-software-sdp

SDP-649

tom_tyler (C. Thomas Tyler)
C. Thomas Tyler created this job 4 years ago
Open
Enhance mkdirs.sh to handle systemd configuration for installed services.

The Helix Installer installs systemd unit files, but the SDP does
not (though it has templates for them).  Thus the systemd config
is only handled for the first instance on a given machine, and
manual configuration of systemd services is required when adding
additional instances. When this feature is implementt, this manual
step will be eliminated.

This change will need to be coordinated with the Helix Installer,
so when it installs versions of SDP after this is deployed, it
defers to SDP to do systemd configuration, that's currently
handled only by the Helix Installer.
Status
Open
Project
perforce-software-sdp
Severity
C
Reported By
C. Thomas Tyler
Reported Date
4 years ago
Modified By
C. Thomas Tyler
Modified Date
4 years ago
Owned By
tom_tyler
Component
core-unix
Type
Feature
robert_cowham (Robert Cowham)
Robert Cowham commented 4 years ago

Yes, and this also needs to handle the case where the OSUSER is not "perforce". That can
lead to some frustration as service will fail to start with misleading error message!

Thus mkdirs.sh should provide and updated p4d_1.service file, and if doing a -test it should
diff it against the existing one.
Reply
tom_tyler (C. Thomas Tyler)
C. Thomas Tyler commented 4 years ago (edited)

All sounds good! The Helix Installer (which already generates systemd service files and accounts for OSUSER) will also need to change. If installing SDP of a greater version than whatever version this change comes in, it'll defer to the SDP for systemd configuration. See job HI-75.
Reply