Bug 50619 - After changing resolv.conf signaling httpd doesn't pick up the changes
Summary: After changing resolv.conf signaling httpd doesn't pick up the changes
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.3
Hardware: PC Linux
: P2 minor (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate, PatchAvailable
Depends on:
Blocks:
 
Reported: 2011-01-19 13:56 UTC by Matt Miller
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments
Patch to add a call to res_init. (995 bytes, patch)
2011-01-19 13:56 UTC, Matt Miller
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Miller 2011-01-19 13:56:21 UTC
Created attachment 26520 [details]
Patch to add a call to res_init.

We use SIGUSR1 to tell Apache to pick up config changes.  After adding nameservers to our resolv.conf we signaled Apache, but it didn't pick up the changes.

Attached patch fixes it for Linux.
Comment 1 Stefan Fritsch 2011-02-03 15:20:18 UTC
Committed to trunk as r1066944
Comment 2 Stefan Fritsch 2011-02-05 14:05:07 UTC
reverted in r1067483

Needs some autoconf foo that works on MaxOS X.
Also, discussion on httpd-dev indicates this should go into APR.
Comment 3 Maciej Deorowicz 2014-10-09 19:37:43 UTC
(In reply to Matt Miller from comment #0)
> We use SIGUSR1 to tell Apache to pick up config changes.  After adding
> nameservers to our resolv.conf we signaled Apache, but it didn't pick up the
> changes.

I observed similar behaviour for httpd-2.4.10 + apr-1.5.1 + apr-util-1.5.3 .
Comment 4 Matt Miller 2014-10-09 20:03:35 UTC
(In reply to Maciej Deorowicz from comment #3)
> I observed similar behaviour for httpd-2.4.10 + apr-1.5.1 + apr-util-1.5.3 .

If you can, it should be easy to restart httpd.
Comment 5 William A. Rowe Jr. 2018-11-07 21:09:56 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.