SDP-353

C. Thomas Tyler
Closed
Avoid doing 'p4d -cset' for P4JOURNAL, but preserve safety feature.

Change @18686 introduced logic in p4d startup to always forcibly
set P4JOURNAL to the correct SDP-defined value, /p4/N/logs/journal,
by using 'p4d -cset' at the start of processing.  This matches
the value set in the SDP shell environment.

This was done to address a situation where, for whatever reason,
P4JOURNAL was somehow set to an incorrect value, with bad
consequences.  Apparently it was set with a 'p4 configure'
command resulting in it being stored in db.config, which
overrides the shell environment setting.

Using 'p4d -cset' generates strange and atypical entries in the
journal file, and so I want to stop doing that.  Also, I want
to avoid defining things in more than one way.

So, we want to change the logic so that we detect the
P4JOURNAL value as set in db.config first.  If it is
set, we should instead to a 'p4d -cunset' to make sure
the value for P4JOURNAL defined in the shell environment
does not get overriden.

While we are at it, we may want to also ensure that P4LOG,
and other key setting are not defined in db.config, so that they
defer to the SDP standard shell environment values.
Status
Closed
Project
perforce-software-sdp
Severity
C
Reported By
tom_tyler
Reported Date
Modified By
tom_tyler
Modified Date
Owned By
tom_tyler
Component
core-unix
Type
Feature