> > The goal of your changes seems really *odd*, to put it lightly. > > Changing a system-wide DNS configuration when a single user logs out. > > Is your intent to restore the DNS configuration when she is no longer > > using the system? > > Now you understand ... almost. I need to have the system-wide DNS > configuration set on that portable for use here. That's neither odd or > strange. I suppose that if one runs all one's LANs using dhcp it's difficult > to appreciate that other networks use static IP addresses. > > All coffee shop wireless access points run DHCP and either blank > /etc/resolv.conf or put in their own list of servers. The problem is that > here the LAN uses static IP addresses, not DHCP, and each host needs the > same /etc/resolv.conf file to access any internal or external host. > > The point of copying /etc/resolv.conf.home to the blank or external > content of /etc/resolv.conf is to allow connection to the local network and > the 'Net from here.
It's not at all odd that you want to have this file restored when you go to a statically assigned network. What is odd is that you're updating it automatically from an individual user's script files. Under Debian and Ubuntu, one can accomplish this kind of update through /etc/network/interfaces. You can also use GUIs like wicd to switch between DHCP network profiles and static network profiles. Or you could look into the suggestions I made about system start up/shut down. What scripts does your distro run when it enables an ethernet interface? All I'm saying is, give us the context and we may be able to suggest things that both make more sense (from security and usability prespective) and are less difficult to configure. tim _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
