Spyke
linux_gaming·Linux GamingbyButteredBread

Esync not changing

Ok so I am on voidlinux. doing "ulimit -Hn" outputs "4096" And I can only move it down until 1024 or whatever with that command but temporally anyways. So I edited /etc/security/limits.conf and added "* hard nofile 1048576" at the end, but nothing happened, I've tried slightly different configurations of the file and still nothing. I have also rebooted multiple times so idk what's wrong.

Solved: First I was trying to change the number of open files limit or whatever apparently, second games still don't work, they're just as laggy and still crash but now without an error message in lutris specifically :thumbs up: Anyways I just followed this quote from the r/voidlinux subreddit “in /etc/pam.d/login add the line session required /lib/security/pam_limits.so to the bottom then do the same for the file associated with your DM i.e. /etc/pam.d/lightdm” and then rebooted or whatever.

View original on sh.itjust.works
24
Comments17
vividspecter
aussie.zone

There's little to no reason to use esync anymore. Use a recent kernel and a recent version of Proton or Wine and you can instead use NTsync which is faster and more reliable.

9
potatoguy
mbin.potato-guy.space

did you try a smaller amount? mine is:

* soft nofile 65535
* hard nofile 65535

Edit: even if you're not going to use esync, some mods and modpacks consume a lot of files.

5
ButteredBreadreply
sh.itjust.works

No it's not that apparently, if I do sudo and enter that one and there I do ulimit -Hn the limit was changed, it just doesn't change for my normal user even if I specify it just for it.

3
potatoguyreply
mbin.potato-guy.space

My /etc/security/limits.conf is like this (everything is commented, just that two lines aren't):

#<domain>      <type>  <item>         <value>
#

#*               soft    core            0
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#@student        -       maxlogins       4

# End of file
* soft nofile 65535
* hard nofile 65535

Idk if you have anything else in that file, but it could be good to try with only that two uncommented lines and then reboot the computer.

4
ButteredBreadreply
sh.itjust.works

well yea

# /etc/security/limits.conf
#
#This file sets the resource limits for the users logged in via PAM.
#It does not affect resource limits of the system services.
#
#Also note that configuration files in /etc/security/limits.d directory,
#which are read in alphabetical order, override the settings in this
#file in case the domain is the same or more specific.
#That means, for example, that setting a limit for wildcard domain here
#can be overridden with a wildcard setting in a config file in the
#subdirectory, but a user specific setting here can be overridden only
#with a user specific setting in the subdirectory.
#
#Each line describes a limit for a user in the form:
#
#<domain>        <type>  <item>  <value>
#
#Where:
#<domain> can be:
#        - a user name
#        - a group name, with @group syntax
#        - the wildcard *, for default entry
#        - the wildcard %, can be also used with %group syntax,
#                 for maxlogin limit
#
#<type> can have the two values:
#        - "soft" for enforcing the soft limits
#        - "hard" for enforcing hard limits
#
#<item> can be one of the following:
#        - core - limits the core file size (KB)
#        - data - max data size (KB)
#        - fsize - maximum filesize (KB)
#        - memlock - max locked-in-memory address space (KB)
#        - nofile - max number of open file descriptors
#        - rss - max resident set size (KB)
#        - stack - max stack size (KB)
#        - cpu - max CPU time (MIN)
#        - nproc - max number of processes
#        - as - address space limit (KB)
#        - maxlogins - max number of logins for this user
#        - maxsyslogins - max number of logins on the system
#        - priority - the priority to run user process with
#        - locks - max number of file locks the user can hold
#        - sigpending - max number of pending signals
#        - msgqueue - max memory used by POSIX message queues (bytes)
#        - nice - max nice priority allowed to raise to values: [-20, 19]
#        - rtprio - max realtime priority
#
#<domain>      <type>  <item>         <value>
#

#*               soft    core            0
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
# End of file
* hard nofile 1048576
* soft nofile 1048576

mine has looked like this for multiple hours and I've rebooted my computer multiple times.

3
potatoguyreply
mbin.potato-guy.space

Did you try with 64k instead of 1 million in the file and rebooting? If that doesn't work, then idk what will work.

4
ButteredBreadreply
sh.itjust.works

No, it didn't work, what I did find weird is that I can login as even root or any other even new user and it says 4096 but if I enter the sudo shell it does the number I put in the file.

3
potatoguyreply
mbin.potato-guy.space

I found something on reddit.

I'll help you in the morning or you can look through my comments in the sub where I've walked others through it. You need to add the pam rules to whatever login manager you're using.

The link they pointed to

2
ButteredBreadreply
sh.itjust.works

It works! :D Quoting the thing "in /etc/pam.d/login add the line session required /lib/security/pam_limits.so to the bottom then do the same for the file associated with your DM i.e. /etc/pam.d/lightdm"

3
ButteredBreadreply
sh.itjust.works

oh yea it's probably something like that, if I go directly to console to login it works like it should, I can't start any DEs like that cuz they're not setup but yea, and I guess the sudo thing works for some weird reason related. Also I think you got like cutoff.

2
kbal
fedia.io

Are you sure you really need 1048576 open files? It seems like a lot. But you'll probably want to set "soft" as well as "hard" limits. Then you need to log in again for the change to take effect.

2
ButteredBreadreply
sh.itjust.works

Also, it did not change. I added "* hard nofile 1048576" "* soft nofile 1048576" to /etc/security/limits.conf and everything else is commented. but ulimit -Hn still outputs 4096 after a reboot.

1
kbalreply
fedia.io

Huh, weird. The only thing I can think of is to check /etc/security/limits.d to see if there's another conf file in there setting it to 4096.

2
ButteredBreadreply
sh.itjust.works

There's just /etc/security/limits.d/25-pw-rlimits.conf and it's just a bunch of pipewire stuff, I didn't even know I had pipewire until now honestly.

1

You reached the end