https://bugzilla.balabit.com/show_bug.cgi?id=130 Summary: Changes to resolv.conf do not apply to DNS resolution Product: syslog-ng Version: 3.0.x Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: Kevin.Guthrie@itron.com Type of the Report: bug Estimated Hours: 0.0 This was seen using 3.0.1 on an ARM processor running Linux 2.6.32. It is linked against glibc 2.11. The unit is an embedded device to run independently. It contains a modem to handle communication with head end systems. The configuration was set up to to use a fully qualified domain name to a UDP port. The unit was booted up originally with an empty /etc/resolv.conf file. The syslog-ng daemon was started up prior to the modem establishing a connection. The resolv.conf file is not populated at the time that the syslog-ng daemon is initialized. Errors in the local log show the DNS failure, as expected. However, after the modem connection is established and the resolv.conf file is updated, syslog-ng continues to fail DNS resolution. Attempts to use SIGHUP against the process do not correct the issue. Only killing and restarting the daemon corrects the issue. That should not be necessary. Based off information found at http://sources.redhat.com/bugzilla/show_bug.cgi?id=3675, syslog-ng needs to call the res_init function in order to allow DNS resolution to succeed. This could be limited to the SIGHUP handler or prior to any attempt to perform DNS resolution. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.