Restart=on-failure ?
Or better yet, fix the actual issue :)
> Op 19 aug. 2020 om 20:37 heeft Olaf Hering het volgende
> geschreven:
>
> Am Wed, 19 Aug 2020 07:06:31 -0600
> schrieb Michael Walter :
>
>> service dnsmasq restart
>
> See systemd.service(5) "Restart=" for details.
>
> Olaf
>
On Wed, Aug 19, 2020 at 12:22:37PM +0200, Olivier wrote:
> Hello,
>
> For some class of devices, I would like to return a DHCP Option value which
> repeats requester's MAC address (with case sensitivity control options).
>
> dhcp-vendorclass=foo,"Foo"
>
Am Wed, 19 Aug 2020 07:06:31 -0600
schrieb Michael Walter :
> service dnsmasq restart
See systemd.service(5) "Restart=" for details.
Olaf
pgpawE8qRQKah.pgp
Description: Digitale Signatur von OpenPGP
___
Dnsmasq-discuss mailing list
20. 8. 19. 오후 10:06에 Michael Walter 이(가) 쓴 글:
Hey there. I am looking for a linux command to auto-restart dnsmasq if it
ever fails. It seems that my Raspberry Pi version fails from time to time.
Looked in the archives but was not able to find any documentation on such a
command. Currently I have
20. 8. 19. 오후 10:06에 Michael Walter 이(가) 쓴 글:
service dnsmasq restart command but really want something to do this
automatically if it ever fails.
ha, my fault!
Might this works, but didn't test it.
while true; do { pidof dnsmasq || { service dnsmasq restart; };
sleep 1; } done
Hey there. I am looking for a linux command to auto-restart dnsmasq if it
ever fails. It seems that my Raspberry Pi version fails from time to time.
Looked in the archives but was not able to find any documentation on such a
command. Currently I have to use the
service dnsmasq restart command but
Hello,
For some class of devices, I would like to return a DHCP Option value which
repeats requester's MAC address (with case sensitivity control options).
dhcp-vendorclass=foo,"Foo"
dhcp-option=vendor:foo,43,"http://1.2.3.4/foo_.cfg"
dhcp-vendorclass=bar,"Bar"
On 18.08.20 12:48, Dave Sullivan wrote:
Was trying to add a custom resolv-conf with multiple search domains.
It doesn't seem like dnsmasq takes into account search setting in the
customer resolv-conf but instead continues to use what is in
/etc/resolv.conf
Any thoughts on this behavior?
