public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dnsmasq: Update to 2.76test10
Date: Thu, 25 Feb 2016 15:06:56 -0600	[thread overview]
Message-ID: <56CF6CF0.5050304@dailydata.net> (raw)
In-Reply-To: <56CF54E7.6050507@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 4099 bytes --]

FYI, I had one time recently when the problem arose on my machine. I
currently have dnsmasq_275_2016_01_16 installed, so I may not be up to date.

Also, I was doing a lot of heavy lifting when I did it, and my router is
so kludged up we can not really depend on it right now for testing. I'm
building a new one, and then I'll rebuild the current one and import the
config. It appeared that it was happening when the number of requests
exceeded a certain threshhold (I was using a recursive DNS server that
is NOT associated with level3 or anything).

However, that one time, which can be explained in many different ways,
is the only one, so I agree this version is running a LOT better.

Rod

On 02/25/2016 01:24 PM, Matthias Fischer wrote:
> Hi,
> 
> as far as I understand your first question: Yes. I think this version is
> running better than the previous. See above: "No issues and no restarts
> needed to fix "frozen" DNS." Sounds good. I'm still having no problems
> at all, too.
> 
> Source for '2.76test10' was uploaded - thanks for reminding me. ;-)
> 
> Next, I changed previous 'new' 2.75-versions to 'superseded'. They don't
> show up anymore in patchwork, I think this was intended?
> 
> The question is: are we interested in the last four patches for
> '2.76test10', that came out a few hours ago?
> 
> I'm building the next version 2.76test10 with these four patches, but if
> you would like to merge the *current* '2.76test10', I think that would
> be ok.
> 
> Best,
> Matthias
> 
> On 25.02.2016 07:24, Michael Tremer wrote:
>> Hi,
>>
>> @Matthias: Is this patch applicable on its own? I would like to merge
>> this as I also have the feeling that the currently shipped version is
>> performing worse for me. I am getting loads of messages from our
>> monitoring... :(
>>
>> Just let me know and I will merge this (make sure the source is
>> uploaded). If not, please send an updated version of this patch. Would
>> you also please mark all previous version as superseeded in patchwork?
>>
>> This should hopefully be shipped with Core Update 99.
>>
>> Best,
>> -Michael
>>
>> On Fri, 2016-02-19 at 21:28 +0100, Matthias Fischer wrote:
>>> This is the latest official test verson, including all previous
>>> patches.
>>>
>>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>>> ---
>>>  lfs/dnsmasq | 9 ++-------
>>>  1 file changed, 2 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/lfs/dnsmasq b/lfs/dnsmasq
>>> index 6417a75..21b7d5c 100644
>>> --- a/lfs/dnsmasq
>>> +++ b/lfs/dnsmasq
>>> @@ -24,7 +24,7 @@
>>>  
>>>  include Config
>>>  
>>> -VER        = 2.76test8
>>> +VER        = 2.76test10
>>>  
>>>  THISAPP    = dnsmasq-$(VER)
>>>  DL_FILE    = $(THISAPP).tar.xz
>>> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>>>  
>>>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>  
>>> -$(DL_FILE)_MD5 = fecf1d0be1266e033872e5ed4cb7fc72
>>> +$(DL_FILE)_MD5 = 4b51474ed6081b18c61407077f254cf7
>>>  
>>>  install : $(TARGET)
>>>  
>>> @@ -73,11 +73,6 @@ $(subst %,%_MD5,$(objects)) :
>>>  $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>>>  	@$(PREBUILD)
>>>  	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf
>>> $(DIR_DL)/$(DL_FILE)
>>> -	cd $(DIR_APP) && patch -Np1 -i
>>> $(DIR_SRC)/src/patches/dnsmasq/001-Fix_FTBFS_on_illumos.patch
>>> -	cd $(DIR_APP) && patch -Np1 -i
>>> $(DIR_SRC)/src/patches/dnsmasq/002-
>>> Make_names_of_ARP_script_actions_consistent.patch
>>> -	cd $(DIR_APP) && patch -Np1 -i
>>> $(DIR_SRC)/src/patches/dnsmasq/003-
>>> Fix_breakage_in_ARP_code_when_IPV6_support_not_compiled_in.patch
>>> -	cd $(DIR_APP) && patch -Np1 -i
>>> $(DIR_SRC)/src/patches/dnsmasq/004-
>>> Avoid_losing_timer_when_deleting_a_RA_context.patch
>>> -	cd $(DIR_APP) && patch -Np1 -i
>>> $(DIR_SRC)/src/patches/dnsmasq/005-Avoid_divide-by-zero_when_dhcp-
>>> range_is_a_whole_slash_64.patch
>>>  	cd $(DIR_APP) && patch -Np1 -i
>>> $(DIR_SRC)/src/patches/dnsmasq-Add-support-to-read-ISC-DHCP-lease-
>>> file.patch
>>>  
>>>  	cd $(DIR_APP) && sed -i src/config.h \
>>
> 

-- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

      reply	other threads:[~2016-02-25 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 20:28 Matthias Fischer
2016-02-24 17:10 ` Kienker, Fred
2016-02-25  6:24 ` Michael Tremer
2016-02-25 19:24   ` Matthias Fischer
2016-02-25 21:06     ` R. W. Rodolico [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56CF6CF0.5050304@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox