Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

systemd: multiple CapabilityBoundingSet statements are not merged #19

Closed
nusenu opened this issue Apr 12, 2015 · 2 comments
Closed

systemd: multiple CapabilityBoundingSet statements are not merged #19

nusenu opened this issue Apr 12, 2015 · 2 comments
Labels
Linux_only upstream workaround_applied

Comments

@nusenu
Copy link
Owner

nusenu commented Apr 12, 2015

systemd 215-14's man page about CapabilityBoundingSet:
This option may appear more than once in which case the bounding sets are merged.

So
CapabilityBoundingSet = cap1 cap2

should be semantically identical to

CapabilityBoundingSet = cap1
CapabilityBoundingSet = cap2

but that is not the case.
nusenu pushed a commit that referenced this issue Apr 12, 2015
workaround systemd bug (#19)
48df0a4
@nusenu
Copy link
Owner Author

nusenu commented Apr 12, 2015

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782479

@nusenu
Copy link
Owner Author

nusenu commented Dec 4, 2015

we no longer ship our own systemd service files

@nusenu nusenu closed this as completed Dec 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Linux_only upstream workaround_applied
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nusenu