i2pd has always been working fine for me with the port's default values of openfiles-cur=8192, openfiles-max=8192 and kern.maxfiles=16000. These values are probably even overkill according to i2pd's documentation.
But I'm not using it for torrenting, and my router is not a floodfill. I guess that torrenting may exhaust available file descriptors pretty quickly. My 2 cents. On 2024-01-27 19:29 beecdadd...@danwin1210.de wrote: > ------------------------------ Original Message ------------------------------ > Subject: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login > From: beecdadd...@danwin1210.de > Date: Sat, January 27, 2024 7:16 pm > To: "Stuart Henderson" <s...@spacehopper.org> > ------------------------------------------------------------------------------ > > this software crashes all lower-bandwidth routers I tried using it on. > my computer crashed a few times, but probably not because of what you said.. I > did have kern.maxfiles set to 65565 or something like that, which probably was > able to cause the crash.. > so I ask how can someone check how many openfiles are supported? What depends > on how many you can have? > > i2pd is something similar to torrenting, but anonymous meaning it protects us > from anyone including abusive governments and people > you make connection to routers(other peers runing I2P software like i2pd) and > do it so many times > how many connections you make depends on how many tunnels you allow (default > 5000) and probably speed bandwidth > > It can use as much as someone allows it.. which be tricky on openbsd because > user has to set openfiles, cannot be flexible at runtime. > and no idea what counts as openfile in i2pd, tunnels? routers maybe, too? so > by default if tunnels 5000 unchange from i2pd.conf, could up to 15k openfiles, > who knows? But default speed is I think 32 KB/sec, which is very low, so > almost everyone increases it. > > would love to know how to find out what best number your computer can handle > openfiles, what about shminfo? maxproc? maxvnodes? somaxconn? > > how can find out max connections my router can handle? maybe router overheat? > he does same with qbittorrent, internet connection goes goodbye > > i2pd very very good project, worked on by Russians, they have no freedom of > speech > > I updated to -current and I still have to set /etc/login.conf.d/i2pd manually, > otherwise I2Pd status is "no descriptors" > > so yes 8192 seems low, not excessive, is similar to running webserver maybe > > and if OpenBSD crashes because of whoops no openfiles to give, CRASH, that is > bad need fix > > hope this helps, thanks for maintance > > >On Thu, January 25, 2024 8:05 am, Stuart Henderson wrote: >> On 2024/01/24 23:06, Klemens Nanni wrote: >> >>> Manual instructions are from 2020, we gained /etc/login.d/* support >>> in 2022, so automate it. >> >> Comsidering that the default kern.maxfiles limit on amd64 is 7030, >> bumping maxfiles in login.conf to 8192 without making the sysctl change means >> that i2pd can consume all FDs in the system. >> >> I think it would be better for the login.conf.d file to stick something >> lower if possible. 8192 seems a bit excessive. Is there someone using this >> software who can confirm how many FDs it *really* is likely to use? >> >> If it really needs this many, perhaps it's better not to automate either >> setting, at least then users who bump into the limits will only have problems >> with i2pd not the rest of the system. >> >>> diff -u -p -r1.3 README --- pkg/README 8 Nov 2022 12:41:42 -0000 >>> 1.3 >>> +++ pkg/README 24 Jan 2024 22:24:29 -0000 >>> @@ -5,20 +5,7 @@ >>> Resource Limits: File Descriptors >>> ================================= >>> >>> >>> -By default, the i2pd process runs in the login(1) class of "daemon". >>> -The default limits on file descriptors are insufficient to run i2pd; >>> instead you -should put the _i2pd user and process in their own login(1) >>> class with tuned -resources. >>> -You should also raise the system-wide maxfiles limit. >>> - >>> -1. Configure i2pd login class in the login.conf(5) file: >>> - >>> - i2pd:\ >>> - :openfiles-cur=8192:\ >>> - :openfiles-max=8192:\ >>> - :tc=daemon: >>> - >>> -2. Adjust kern.maxfiles, if needed: >>> +You should raise the system-wide maxfiles limit: >>> >>> >>> # sysctl kern.maxfiles=16000 >>> # echo "kern.maxfiles=16000" >> /etc/sysctl.conf >>> Index: pkg/i2pd.login >>> =================================================================== >>> RCS file: pkg/i2pd.login >>> diff -N pkg/i2pd.login --- /dev/null 1 Jan 1970 00:00:00 -0000 >>> +++ pkg/i2pd.login 24 Jan 2024 22:23:46 -0000 >>> @@ -0,0 +1,4 @@ >>> +i2pd:\ >>> + :openfiles-cur=8192:\ >>> + :openfiles-max=8192:\ >>> + :tc=daemon: >>> >>> >> >>
