Timeline for Kernel inotify watch limit reached
Current License: CC BY-SA 3.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2024 at 12:59 | comment | added | Mugen |
Worth mentioning you need to run sysctl -p also for the temp solution, for changes to apply
|
|
| Aug 1, 2022 at 8:14 | comment | added | Jonathan | I recursively watched 50000 files in a directory in Ubuntu 20 and the was far less than 1kb per file as suggested above. It used about 5MB. | |
| May 12, 2021 at 18:33 | comment | added | Karel Vlk |
Did you mean -f1 instead of -f3?
|
|
| Oct 23, 2017 at 9:32 | comment | added | Tobias Gaertner | +1 Debian-Version works for current Ubuntu-Based (for its based on Debian) Systems. I needed the higher value for indexing a big git repo via gitkraken (git-gui) | |
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Apr 13, 2017 at 12:22 | history | edited | CommunityBot |
replaced http://askubuntu.com/ with https://askubuntu.com/
|
|
| S Feb 8, 2017 at 15:35 | history | suggested | Dani | CC BY-SA 3.0 |
Fix confusion between systemd and sysctl
|
| Feb 8, 2017 at 15:07 | review | Suggested edits | |||
| S Feb 8, 2017 at 15:35 | |||||
| Jan 8, 2017 at 22:55 | comment | added | tshepang | @stackexchanger if you very sure that these are similar (e.g. you've tested), then please submit and edit to the Question. I myself haven't checked, and I know that distros tend to patch packages, so behavior could be different for the same packages. This is not to mention differences in package versions as well. | |
| Jan 6, 2017 at 23:46 | comment | added | stackexchanger | Note that what you describe as "Debian/RedHat" and "Arch" are more precisely SysV and systemd systems, respectively. Debian-based systems now use systemd, so the "Arch" method is preferrable for them. | |
| Dec 9, 2016 at 13:42 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 |
simplified find, note that the number is not the number watches.
|
| S Nov 13, 2016 at 12:36 | history | suggested | Qw3ry | CC BY-SA 3.0 |
As stated in the comments the "permanent" solution is not permanent at all. Provided instructions for a really permanent change
|
| Nov 13, 2016 at 11:45 | review | Suggested edits | |||
| S Nov 13, 2016 at 12:36 | |||||
| Oct 17, 2016 at 15:00 | comment | added | user3467349 |
You should uniq before you run ps otherwise this can take very long.
|
|
| Aug 10, 2016 at 14:37 | review | Suggested edits | |||
| Aug 10, 2016 at 15:12 | |||||
| May 7, 2016 at 4:38 | comment | added | Merc |
"Permanently: Replace the value within the /proc/sys/fs/inotify/max_user_watches" <-- this is incorrect. To make this permanent you need to change /etc/sysctl.conf
|
|
| Apr 19, 2015 at 18:23 | comment | added | CodeGnome |
Other people might run into this, too. The ps command above says error: process ID list syntax error with procps-ng version 3.3.9 on Ubuntu.
|
|
| S Feb 27, 2015 at 23:19 | history | edited | HalosGhost | CC BY-SA 3.0 |
Added more/updated info on inotify watches, how to check max, set max, check ussage, and see if limit is reached. Used info from http://askubuntu.com/questions/154255/how-can-i-tell-if-i-am-out-of-inotify-watches https://github.com/atom/atom/issues/2082#issuecomment-55533087; code block for command
|
| S Feb 27, 2015 at 23:19 | history | suggested | Obsidian Jackal | CC BY-SA 3.0 |
Added more/updated info on inotify watches, how to check max, set max, check ussage, and see if limit is reached. Used info from http://askubuntu.com/questions/154255/how-can-i-tell-if-i-am-out-of-inotify-watches https://github.com/atom/atom/issues/2082#issuecomment-55533087
|
| Feb 27, 2015 at 23:11 | review | Suggested edits | |||
| S Feb 27, 2015 at 23:19 | |||||
| S Dec 1, 2014 at 12:10 | history | edited | slm♦ | CC BY-SA 3.0 |
Deprecating /etc/sysctl.conf, as this solution isn't working as of today.
|
| S Dec 1, 2014 at 12:10 | history | suggested | Antoine | CC BY-SA 3.0 |
Deprecating /etc/sysctl.conf, as this solution isn't working as of today.
|
| Dec 1, 2014 at 12:01 | review | Suggested edits | |||
| S Dec 1, 2014 at 12:10 | |||||
| Jul 10, 2011 at 5:14 | comment | added | beatgammit | @ultrasawblade- inotify replaced dnotify. dnotify was slow and buggy. inotify can be used on directories, and a directory will be "changed" when one of the files in that directory (one level deep) is modified. Directories are just files anyway. | |
| Jun 16, 2011 at 13:36 | comment | added | LawrenceC |
Isn't there also a dnotify that works the same, but on directories? Maybe consolidate multiple files you are inotifying into a single directory?
|
|
| Jun 16, 2011 at 11:48 | vote | accept | Ultraspider | ||
| May 25, 2011 at 20:55 | comment | added | Falmarri |
I guess very few codes need the values higher than the default Dropbox may require a higher limit, depending on how many files you have. Iv'e raised mine with no issues. in fact, the dropbox notification (that occurs when it reaches its limit) explicitly tells you to raise it.
|
|
| May 25, 2011 at 13:26 | history | edited | tshepang | CC BY-SA 3.0 |
added 150 characters in body; deleted 3 characters in body; deleted 2 characters in body
|
| May 25, 2011 at 13:21 | history | answered | tshepang | CC BY-SA 3.0 |