Closed
Bug 993684
Opened 11 years ago
Closed 11 years ago
Add a 'relengapi' user to run the relengapi wsgi processes
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
We've already done this for buildapi, so it's no big thing to do again for relengapi. It gives some isolation between the services.
Updated•11 years ago
|
Assignee: relops → dustin
Assignee | ||
Comment 1•11 years ago
|
||
Jabba, you set up the 'buildapi' user in LDAP for me. Can you do the same for 'relengapi', and reassign? Thanks!
Assignee: dustin → jdow
Comment 2•11 years ago
|
||
I've cloned the buildapi user to relengapi (with new uidNumber, etc.). It's not a member of any groups, not sure if that's needed.
Assignee: jdow → dustin
Assignee | ||
Comment 3•11 years ago
|
||
OK, it's running as relengapi now. Thanks Jabba!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•