On Wed, Jun 12, 2013 at 01:42:58PM +0200, Tollef Fog Heen wrote: > I'm not sure why you think systemd changes anything here?
One of the main purposes of systemd is to eliminate dependencies and fulfil them with socket activation. When converting init scripts to .service files, this will likely mean dropping $named for a number services. With the current resolvconf integration of some dns caches, the /etc/resolv.conf will only be usable after the dns cache has been started. This exposes those services formerly depending on $named to the dynamic nature of /etc/resolv.conf. All that I am aiming for is to declare one of the following practises as broken: * Treating an empty /etc/resolv.conf as a permanent error or failing to discover changes in /etc/resolv.conf later on. * Changing /etc/resolv.conf during startup of a local dns cache. So if /etc/resolv.conf is declared to be static (A), then the second practise is broken. And if dynamic modifications are to be supported (B), then the first practise is broken. Helmut -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130612123436.GA12811@localhost
