beerman has quit [Quit: Bridge terminating on SIGTERM]
beerman has joined #crux-devel
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-devel
PT has joined #crux-devel
<jaeger>
adding 'session required pam_limits.so' to /etc/pam.d/common-session doesn't seem to cause any issues for me (none expected, really) and also allows settings in /etc/security/limits.conf to actually work, so seems like a good idea to me. Anyone object to me adding that to linux-pam?
<beerman>
absolutely not
<jaeger>
defaults in limits.conf are commented out and limits.d has nothing in it by default, so shouldn't cause any issues, I think
<beerman>
agreed
<SiFuh>
jaeger: are the settings going to be default or CRUX specific?
<SiFuh>
I am assuming they will be default and commented out
<jaeger>
I would not make any changes other than that one line in common-session
<jaeger>
I much prefer to leave those choices to the user
<jaeger>
Without it, though, setting things like nofile via security.conf doesn't work
<jaeger>
er, limits.conf
<jaeger>
try adding '<username> hard nofile 524288' to limits.conf and then running 'ulimit -Hn' as that user without it, you won't see the limit change
PT has quit [Quit: Leaving]
<jaeger>
I'm not sure how to actually test esync with wine but at least it doesn't break other stuff so far
<beerman>
I have no idea, it just seems like lutris wants to enforce best practices they collected on the winehq wiki etc.. you can't override it either but all I can say is overwatch just works and thats fine