Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15320 - [glibc] should re-read resolv.conf before each resolving [patch included]

Attached to Project: Arch Linux
Opened by Tomas Mudrunka (harvie) - Tuesday, 30 June 2009, 12:19 GMT
Last edited by Allan McRae (Allan) - Tuesday, 30 June 2009, 14:03 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Programs should reload /etc/resolv.conf when it changes
more info (+patch) here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272265

in short: sometimes this causes need to restart some appliactions even some network daemons. in arch i had problems for example with:
firefox, totem, pidgin, miredo (1st 3 apps were problematic only without networkmanager)

Additional info:
* package version(s)
-- core/glibc 2.10.1-2 (base)
* config and/or log files etc.


Steps to reproduce:
1.) launch some application when connected to network
2.) connect to another network with different dns server ipaddress (and edit /etc/resolv.con properly)
or
1.) connect with networkmanager to some network
2.) launch some network application without networkmanager support
3.) connect to another network with different dns server ipaddress
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 30 June 2009, 14:03 GMT
Reason for closing:  Won't fix
Additional comments about closing:  See comments
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 30 June 2009, 13:48 GMT
  • Field changed: Summary ([libc] should re-read resolv.conf before each resolving [patch included] → [glibc] should re-read resolv.conf before each resolving [patch included])
For these type of purposes try to use nscd ;) "/etc/rc.d/nscd start" or add to rc.conf

Cite manpage:
The daemon will try to watch for changes in configuration files appropriate for each database (e.g. /etc/passwd for the passwd database or
/etc/hosts and /etc/resolv.conf for the hosts database), and flush the cache when these are changed. However, this will happen only after a
short delay (unless the inotify(7) mechanism is available and glibc 2.9 or later is available), and this auto-detection does not cover configura-
tion files required by non-standard NSS modules, if any are specified in /etc/nsswitch.conf. In that case, you need to run the following command
after changing the configuration file of the database so that nscd invalidates its cache:

$ nscd -i <database>

Comment by Allan McRae (Allan) - Tuesday, 30 June 2009, 14:02 GMT
Agree that this is how to deal with this. That appears to be upstream's opinion too (from the mailing list thread in the very old Debian bug report linked above). Given we try to stay as vanilla as possible, I am closing as Won't Fix.

Loading...