j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMT<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=299.msg2406#msg2406">Quote from: Xunie on July 12, 2010, 10:27:53 PM</a></div><div class="quote">It automatically raises it, I don't think nice 20 ./bitcoin will help to be honest.<br/>I think some people have set higher priorities for themselves in /etc/security/limits.conf, and when -20 isn't available as a nice level, a lower priority is tried.<br/>So, I think the dirty hack of editing /etc/security/limits.conf might fix it.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=299.msg2386#msg2386">Quote from: lachesis on July 12, 2010, 09:29:03 PM</a></div><div class="quote">I wondered about that, but I've never noticed any issues on a dual-core 64bit system.<br/></div>I don't have any problems on my quad core system here either!<br/></div><br/>That may be the issue because you can't "Nice 20" anything, 19 is the max <img alt="Wink" border="0" src="/static/img/emoticons/wink.gif"/><br/><br/>So far, I've "Nice 19" 3 clients (one 64 bit and two 32 bit) for the last hour and they haven't changed the Nice level on me yet.<br/><br/>I figured since the process is started at that level, it would remain for all child processes spawned afterwards. I could be wrong though, I'll check again in another few hours to see.</div> text/html
https://whatsonchain.com/tx/e30e58122cd8ea814ec4ec1bbe7a00e5faeb2023d09147d54378629ae5d5f9dc