• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Explanation for Plesk 17 nicing httpd processes to 10

HostaHost

Regular Pleskian
Hello, I can't find any mention of this in the release notes or online docs, but it seems that Plesk 17 has added a behavior that starts apache reniced to 10 instead of standard priority. This has the effect of causing all spawned cgi scripts to also run at a nice value of 10.

This may be problematic for some, so I was curious if there's any official explanation of why this was done and if there's a way to undo it besides setting NICELEVEL in /etc/sysconfig/httpd?
 
Back
Top