<div dir="ltr">Hello,<div><br></div><div>As discussed here: <a href="https://github.com/pi-hole/FTL/issues/703">https://github.com/pi-hole/FTL/issues/703</a><br></div><div><br></div><div>At startup, dnsmasq tries to close all file descriptors from 0 to `ulimit -n` (the maximum number of open files) - here <a href="http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blob;f=src/dnsmasq.c;h=573aac069b75b801ad1ddf5305af5010ca1ab88a;hb=HEAD#l151">http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blob;f=src/dnsmasq.c;h=573aac069b75b801ad1ddf5305af5010ca1ab88a;hb=HEAD#l151</a><br><br>On setups where this limit is high, this takes a large amount of time - or even "hangs" indefinitely. Docker sets this limit to ~1M for instance - and the kubernetes setup I am using (k3s) is setting it to "Infinity", which translates to 1073741816.<br><br>I would suggest switching over to something based on the actually open files - like was done for the rpm package: cf <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1537564">https://bugzilla.redhat.com/show_bug.cgi?id=1537564</a> and <a href="https://github.com/rpm-software-management/rpm/pull/444/files">https://github.com/rpm-software-management/rpm/pull/444/files</a> for an actual patch<br><br>Work around is to run a `ulimit -n 1024` before starting dnsmasq - but that's not really a clean solution.<br></div><div><br></div><div>Thanks!</div><div>Arthur</div></div>