> Le 23 sept. 2016 à 07:36, Erich Titl <erich.t...@think.ch> a écrit :
> 
> Am 23.09.2016 um 10:13 schrieb Erich Titl:
>> Am 23.09.2016 um 00:38 schrieb Jean-Roch Blais:
>>> 
> ...
>> 
>> As I said previously a daemon process _should_ watch its dependencies,
>> often they do not and I don't know if dnsmasq does. The drawback of the
>> bazaar model often is the lack of precise specs, so we cannot easily
>> know if a product was built to specs (if there are any).
>> 
> 
> I looked at dnsmasq and _it_does_ poll the resolver files (as it states
> in the log anyway) so this is not an issue, but yes, it will fail to
> start if the resolver file is missing.
> 

if you look back at the log it says:

Sep 18 15:28:14 firewall dhcpcd[11737]: version 6.7.1 starting
Sep 18 15:28:14 firewall dhcpcd[11737]: forked to background, child pid 11740
Sep 18 15:28:14 firewall dnsmasq[11765]: directory /etc/dhcpc/resolv.conf for 
resolv-file is missing, cannot poll
Sep 18 15:28:14 firewall dnsmasq[11765]: FAILED to start up
you see that dnsmasq complains it doesn’t even find the directory 
/etc/dhcpc/resolv.conf, and hence the file. It looks as if the #background fix 
might not be that bad after all… if slows down dnsmasq but more importantly it 
gives time to dhcpcd to create the dir and the file ! 

I was wondering, as a test, if in the init.d we could have a small process to 
"touch /etc/dhcpc/resolv.conf" before dnsmasq starts, dnsmasq would find the 
file empty, and try to read it later, I saw it do that in BUC 5.1.7 ! Is it 
possible to do that without making an lrp package, just using local save of an 
eventual /etc/init.d/touch.sh :-) ?

I hope you’r all having fun with this !!! Since it now works for me, I don’t 
want you to loose your precious time on a ~solved problem, and I would leave it 
at that.

Aurevoir !
jrb.

 <>I _believe_ we should take care of this in the init script which could
> provide a loop with a timeout before attempting to start dnsmasq, so
> this could be handled more gracefully.
> 
> cheers
> 
> Erich
> 
> 
> ------------------------------------------------------------------------------
> ------------------------------------------------------------------------
> leaf-user mailing list: leaf-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-user
> Support Request -- http://leaf-project.org/

------------------------------------------------------------------------------
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to