kthxbye
Opps, forgot to add the arches. My bad.
Stable on Alpha.
x86 done
ppc done
stable on ppc64, but given the way resolvconf works and that it isn't documented in the 2006.1 handbook I wonder if this package shouldn't be masked on releases prior to 2007.0. Not a fun surprise for the average bear when their resolv.conf file disppears on them. :-)
(In reply to comment #5) > stable on ppc64, but given the way resolvconf works and that it isn't > documented in the 2006.1 handbook I wonder if this package shouldn't be masked > on releases prior to 2007.0. > > Not a fun surprise for the average bear when their resolv.conf file disppears > on them. :-) /etc/resolv.conf should never disappear with resolvconf And, resolvconf only updates it when requested. What exact issue are you trying to describe here?
sparc stable.
IA64 stable.
Stable for HPPA.
(In reply to comment #6) > /etc/resolv.conf should never disappear with resolvconf > And, resolvconf only updates it when requested. What exact issue are you trying > to describe here? For me - after a hard crash when using Cisco's VPN client, my resolv.conf vanished and it hasn't been regenerated ever since. I haven't had time to see how to fix this yet, anyway: # pwd /etc ls -l resolv* resolvconf: total 0 drwxr-xr-x 2 root root 6 Apr 10 2006 resolv.conf.d lrwxrwxrwx 1 root root 24 Jan 1 20:16 run -> ../../var/run/resolvconf drwxr-xr-x 2 root root 6 Apr 10 2006 update-libc.d drwxr-xr-x 2 root root 17 Jan 1 20:20 update.d Running resolvconf -u does not restore the resolv.conf. Right now I have manually generated resolv.conf. If I bring interface down and back up my manual resolv.conf vanishes again. I suppose I should just put resolv.conf symlink back and problem would be solved but it bothers me why resolvconf does not regenerate it automatically. More information: The stuff at /var/run/resolvconf seems fine - ./interfaces/wlan contains the correct servers learned via DHCP. If I copy this file to /etc/resolv.conf everything works for a while. # pwd /var/run/resolvconf # ls -R -l .: total 4 -rw-r--r-- 1 root root 5 Jan 26 15:13 added_order drwxr-xr-x 2 root root 17 Jan 26 15:13 interfaces ./interfaces: total 4 -rw-r--r-- 1 root root 113 Jan 26 15:13 wlan
Ok - now that I've actually looked at the code at /etc/resolvconf/update.d/libc, it contains at the very beginning [[ $(readlink /etc/resolv.conf 2>/dev/null) \ != "resolvconf/run/resolv.conf" ]] && exit 0 So if some misbehaving thing that is not using resolvconf screws things up withour properly restoring the previous state (such as a hard-crashing VPN client - so it does not restore the symlink), resolvconf breaks. How about some new rc-parameter, FORCE_RESOLVCONF_SYMLINK or something...?
(In reply to comment #11) > How about some new rc-parameter, FORCE_RESOLVCONF_SYMLINK or something...? Possibly. However, that should not affect 1.2 from being marked stable as it's not a regression. You should open a new bug requesting this enchancement.
amd64 stable
mips stable.
