On 08.02.22 19:32, Ed W wrote:
This is never going to get high enough up my todo list to try, but I did wonder
if a simple
"clustered" system could be built using DBUS or similar events. When a lease is
allocated DBUS (and
a script) is run notifying about that. A little daemon could then use
Simon,
This is never going to get high enough up my todo list to try, but I did wonder
if a simple
"clustered" system could be built using DBUS or similar events. When a lease is
allocated DBUS (and
a script) is run notifying about that. A little daemon could then use this hook
to notify
On Tue, 2022-02-08 at 10:44 +, Simon Kelley wrote:
> Please could you send the entire strace, to me direct if you prefer.
> It's much easier to work out what file descriptor is in use, than
> therefore which code is broken if you have the syscalls that create
> them.
Sure, I will send you
On 07/02/2022 07:56, Ken Gillett via Dnsmasq-discuss wrote:
On MacOS, dnsmasq is started and run by launchd, so launchctl would normally be
used to stop and start. Instead however, a simple 'killall dnsmasq' will stop
it and launchd will automatically restart it. Does it matter to dnsmasq
My long delayed move is suddenly on again, so I'm likely to be absent
for a little while. At least until I can organise am Internet connection
halfway up an Irish mountain.
Simon.
___
Dnsmasq-discuss mailing list
Please could you send the entire strace, to me direct if you prefer.
It's much easier to work out what file descriptor is in use, than
therefore which code is broken if you have the syscalls that create them.
Cheers,
Simon.
On 08/02/2022 09:55, Charlie Turner wrote:
`dnsmasq' has
`dnsmasq' has regressed in its handling of SIGHUP between 2.85 and
2.86. The `strace' record shows correct behaviour.
When `dnsmasq' boots, but before serving any `BOOTP=/=DHCP' requests, I
can send as many `SIGHUPs' as I like to have the service reread its
configuration files without restarting
