This is merged by
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=762a3f243099d26b1e87aad2b1b4b696cd8c33ac
Simon has added description for it.
On 06. 02. 24 0:15, Heikki Linnakangas wrote:
On 05/02/2024 22:52, Geert Stappers wrote:
On Mon, Feb 05, 2024 at 08:47:54PM +0200, Heikki
On 05/02/2024 22:52, Geert Stappers wrote:
On Mon, Feb 05, 2024 at 08:47:54PM +0200, Heikki Linnakangas wrote:
diff --git a/src/inotify.c b/src/inotify.c
index a944c62..0c775de 100644
--- a/src/inotify.c
+++ b/src/inotify.c
@@ -94,7 +94,7 @@ void inotify_dnsmasq_init()
if (daemon->inotifyfd
On Mon, Feb 05, 2024 at 08:47:54PM +0200, Heikki Linnakangas wrote:
>
> If dnsmasq is used in DHCP-only mode, i.e. --port==0, resolv.conf is
> not used for anything. No need to set up inotify watch on it in that
> case.
> ---
> src/inotify.c | 2 +-
> src/dnsmasq.c | 4 ++--
> 2 files changed, 3
Hi,
I'm using dnsmasq as a DHCP server only, with --port=0. My system has
very low limits on inotify watches, and sometimes it fails to start up with:
dnsmasq: failed to create inotify: No file descriptors available
I could raise the limits with systctl, but I started to wonder why
dnsmasq
