diff options
| author | Eric Wong <e@80x24.org> | 2023-03-28 11:12:36 +0000 |
|---|---|---|
| committer | Eric Wong <e@80x24.org> | 2023-03-29 04:36:42 +0000 |
| commit | 687f579ab401cc9ddf63e9901c37c37ab7d4eef1 (patch) | |
| tree | d694b635940db1239109eaabc2268813c8e84e1b /MANIFEST | |
| parent | 6061f4e7b3c68bb4f41960c4df2c1eddcbdc86d9 (diff) | |
| download | public-inbox-687f579ab401cc9ddf63e9901c37c37ab7d4eef1.tar.gz | |
As encountered by Louis DeLosSantos, Linux inotify is capped by
a lesser-known limit than the standard RLIMIT_NOFILE (`ulimit -n`)
value. Give the user a hint about the fs.inotify.max_user_instances
sysctl knob on EMFILE, since EMFILE alone may mislead users into
thinking they've hit the (typically higher) RLIMIT_NOFILE limit.
I can test this on my system using:
perl -I lib -MPublicInbox::Inotify -E \
'my @x = map { PublicInbox::Inotify->new } (1..128)'
But I hesitate to include it in the test suite since triggering
the limit can cause unrelated processes to fail.
Link: https://public-inbox.org/meta/CAE6jdTo8iQfNM9Yuk0Dwi-ARMxmQxX-onL8buXcQ9Ze3r0hKrg@mail.gmail.com/
Reported-by: Louis DeLosSantos <louis.delos@gmail.com>
Diffstat (limited to 'MANIFEST')
| -rw-r--r-- | MANIFEST | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -217,6 +217,7 @@ lib/PublicInbox/In2Tie.pm lib/PublicInbox/Inbox.pm lib/PublicInbox/InboxIdle.pm lib/PublicInbox/InboxWritable.pm +lib/PublicInbox/Inotify.pm lib/PublicInbox/InputPipe.pm lib/PublicInbox/Isearch.pm lib/PublicInbox/KQNotify.pm |