Bug #15892
closed
global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred
Added by Nathan Cutler almost 8 years ago.
Updated almost 8 years ago.
Description
kmroz writes in https://github.com/ceph/ceph/pull/8702
As part of deferred setuid/setgid, we also need to chown the run_dir if specified in the config. This ensures that asok files created in a custom run_dir are ultimately owned by the correct user:group.
- Copied to Backport #15893: jewel: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added
- Status changed from Pending Backport to Duplicate
- Backport deleted (
jewel)
- Copied to deleted (Backport #15893: jewel: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred)
- Project changed from Ceph to devops
- Project changed from devops to Ceph
- Related to Bug #15607: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
- Related to deleted (Bug #15607: Ownership of run dir, pid file and asok file not set when deferring permissions drop)
- Is duplicate of Bug #15607: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
Also available in: Atom
PDF