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.

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

Add CAP_SYS_NICE to FTL's capabilities #3455

Merged
merged 1 commit into from
May 28, 2020
Merged

Conversation

DL6ER
Copy link
Member

@DL6ER DL6ER commented May 28, 2020

By submitting this pull request, I confirm the following:

  • I have read and understood the contributors guide, as well as this entire template.
  • I have made only one major change in my proposed changes.
  • I have commented my proposed changes within the code.
  • I have tested my proposed changes, and have included unit tests where possible.
  • I am willing to help maintain this change if there are issues with it later.
  • I give this submission freely and claim no ownership.
  • It is compatible with the EUPL 1.2 license
  • I have squashed any insignificant commits. (git rebase)

What does this PR aim to accomplish?:

Allow FTL to control its own niceness in pi-hole/FTL#798

How does this PR accomplish the above?:

Add CAP_SYS_NICE to FTL's capabilities so it can control its own niceness.

What documentation changes (if any) are needed to support this PR?:

None

@DL6ER DL6ER added this to the v5.1 milestone May 28, 2020
@DL6ER DL6ER requested a review from a team May 28, 2020 19:19
@DL6ER DL6ER merged commit 5dc7ec0 into development May 28, 2020
@DL6ER DL6ER deleted the tweak/FTL_niceness branch May 28, 2020 20:00
@PromoFaux PromoFaux mentioned this pull request Jul 5, 2020
@pralor-bot
Copy link

This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pi-hole-5-1-released/35577/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants