First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 72400
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Jon Portnoy (RETIRED) <avenj@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Bel Zébute <stephane@gorfou.ca>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
dnsmasq /etc/init.d/dnsmasq text/plain Bel Zébute 2004-11-24 15:02 0000 600 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 72400 depends on: Show dependency tree
Bug 72400 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-11-24 14:59 0000 
dnsmasq can receive a SIGHUP to fluch it's cache and reload the config files
while still resolvinf name.  The stop/start approach will temporarely leave the
network with no dns server.

Reproducible: Always
Steps to Reproduce:

------- Comment #1 From Bel Zébute 2004-11-24 15:02:11 0000 ------- 
Created an attachment (id=44678) [edit]
/etc/init.d/dnsmasq

Maybe there's a better way to do this.

------- Comment #2 From basic 2005-08-24 06:08:22 0000 ------- 
probably something along the lines of 

kill -HUP `cat /var/run/dnsmasq.pid`

is what you are looking for.

------- Comment #3 From Daniel Black 2005-12-29 02:24:51 0000 ------- 
Looks weird but this also works

start-stop-daemon --stop -s HUP -p /var/run/dnsmasq.pid

------- Comment #4 From Jon Portnoy (RETIRED) 2006-01-07 17:39:59 0000 ------- 
Whoa, ancient bug.. Fixed now, no revision bump since I think most of our
dnsmasq users are capable of using killall -HUP ;)

Sorry about the delay, bug mail tends to get lost
First Last Prev Next    No search results available      Search page      Enter new bug