ulimit restricted after starting sway

[honza]

sway version 1.0-rc1-177-gacdb4ed7 (Mar 16 2019, branch 'master')

1. Computer boots into tty
2. ulimit -n says 50,000
3. Start sway with sway
4. ulimit -n says 1024

Any ideas?

[emersion]

Maybe it's because sway is suid or has caps?

[honza]

How can I verify these things? The "s" ins't in the output of of ls -l $(which sway).

[emersion]

What about getcap /usr/bin/sway?

[honza]

Empty output

[emersion]

Beats me then

[honza]

Beats me then

Thanks for trying!

[schauveau]

You may want to have a look at /proc/PID/limits for various processes (sway, shells, ...). That could give you some clues to figure out what is causing that.
My bet would be for PAM via some config files in /etc/security/

[mstoeckl]

I ran into a similar issue, except with ulimit -c changing; according to strace sway,

prlimit64(0, RLIMIT_CORE, {rlim_cur=0, rlim_max=0}, NULL) = 0

was being called. Identifying the calling point by running sway with gdb and catch syscall 302 revealed that I had been building with AddressSanitizer enabled, and that its initialization routines were responsible.

[BoostCookie]

For me Lutris is complaining when I try to start a game.
https://github.com/lutris/docs/blob/master/HowToEsync.md

To work around sway resetting the limits, I start lutris via

sudo -u $(whoami) -E lutris

After sudo the limits are the ones I set in /etc/security/limits.conf

% ulimit -Hn
4096
% sudo -u $(whoami) -E sh -c "ulimit -Hn"
1048576