Actions
Bug #15607
closedOwnership of run dir, pid file and asok file not set when deferring permissions drop
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If a daemon requests to defer permissions drop (as is the case with radosgw), we need to take care of properly chown()'ing the run directory, pid file and admin socket (asok) file.
Updated by Anonymous almost 8 years ago
- Status changed from New to Pending Backport
- Backport set to jewel
Updated by Nathan Cutler almost 8 years ago
- Copied to Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
Updated by Nathan Cutler almost 8 years ago
master PR: https://github.com/ceph/ceph/pull/8702
Updated by Nathan Cutler almost 8 years ago
- Related to Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added
Updated by Nathan Cutler almost 8 years ago
- Related to deleted (Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred)
Updated by Nathan Cutler almost 8 years ago
- Has duplicate Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added
Updated by Loïc Dachary almost 8 years ago
- Copied to Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
Updated by Loïc Dachary almost 8 years ago
- Status changed from Pending Backport to Resolved
Actions