Bug #15607
closed
Ownership of run dir, pid file and asok file not set when deferring permissions drop
Added by Anonymous about 8 years ago.
Updated almost 8 years ago.
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.
- Status changed from New to Pending Backport
- Backport set to jewel
- Copied to Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
- Project changed from devops to Ceph
- Related to Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added
- Related to deleted (Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred)
- Has duplicate Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added
- Copied to Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF