SDP-331
Closed
DOC: lack of clarity on folder ownership.
Make this [/hxdepots/sdp] directory writable - to whom? And what are the full permissions? Does it need to be owned by 'p4admin' or (if you're using the script default) 'perforce'?
Is this not handled by the mkdirs script alongside the other /hx directories?
UPDATE: reopened - the SDP Guide still states "make the entire $SDP directory writable" but doesn't clarify ownership, nor if this is handled by the mkdirs script.
Make this [/hxdepots/sdp] directory writable - to whom? And what are the full permissions? Does it need to be owned by 'p4admin' or (if you're using the script default) 'perforce'?
Is this not handled by the mkdirs script alongside the other /hx directories?
UPDATE: reopened - the SDP Guide still states "make the entire $SDP directory writable" but doesn't clarify ownership, nor if this is handled by the mkdirs script.
- Status
- Closed
- Project
- perforce-software-sdp
- Severity
- B
- Reported By
- Adam Morriss
- Reported Date
- 7 years ago
- Modified By
- swarm-user
- Modified Date
- 3 years ago
- Owned By
- amo
- Component
- doc
- Type
- Bug
@amo Thanks! Clarifying text added.
I am leaving out a discussion of the mkdirs.sh script in the step where we're doing the 'chmod -R +w $SDP', since these bootstrapping steps are done prior to the mkdirs.sh being made ready. There is overlap with what mkdirs.sh does later, but that's later in the process. At this point in the process, we're just getting setup to be able to run mkdirs.sh. The next step starts describing how to use mkdirs.sh that was just unpacked from the tarball.