SDP-626
Punted
Fix p4d_base incorrectly calling systemctl to check on status.
This causes "sudo systemctl start p4d_1" to start and immediately stop the service. This makes the system unusable!
The problem is incorrect detection of systemd being in use and thus -d or --daemonsafe flags being used when they shouldn't be.
This causes "sudo systemctl start p4d_1" to start and immediately stop the service. This makes the system unusable!
The problem is incorrect detection of systemd being in use and thus -d or --daemonsafe flags being used when they shouldn't be.
- Status
- Punted
- Project
- perforce-software-sdp
- Severity
- A
- Reported By
- Robert Cowham
- Reported Date
- 4 years ago
- Modified By
- C. Thomas Tyler
- Modified Date
- 4 years ago
- Owned By
- robert_cowham
- Dev Notes
- 2021/04/23 ttyler: Per discussion with Robert, dropping Severity
on this and punting. While it appeared to be a Sev A, it was actually
a minor configuration issue.
In place of this proposed change will be the following:
SDP-627: Add verify_sdp.sh check for p4*.services files w/o world read access. - Type
- Bug
Log in to comment