Why hasn't this bug been fixed yet? (as of dhcp3_3.0+3.0.1rc11)
The original poster has given a perfectly good fix, although I prefer:
make_resolv_conf() {
if [ "x$new_domain_name_servers" != x ] || ["x$new_domain_name" != x
] ; then
rm -f /etc/resolv.conf
if [ "x$new_domain_name" != x ]; then
echo search $new_domain_name >/etc/resolv.conf
fi
if [ "x$new_domain_name_servers" != x ]; then
for nameserver in $new_domain_name_servers; do
echo nameserver $nameserver >>/etc/resolv.conf
done
fi
chmod 644 /etc/resolv.conf
fi
}
Since it makes new_domain_name_servers and new_domain_name independent.
Anyway, back to the point. Is there a reason why this bug has not been
fixed?
Why hasn't this bug been fixed yet? (as of dhcp3_3. 0+3.0.1rc11)
The original poster has given a perfectly good fix, although I prefer:
make_resolv_conf() { domain_ name_servers" != x ] || ["x$new_ domain_ name" != x domain_ name_servers" != x ]; then name_servers; do
if [ "x$new_
] ; then
rm -f /etc/resolv.conf
if [ "x$new_domain_name" != x ]; then
echo search $new_domain_name >/etc/resolv.conf
fi
if [ "x$new_
for nameserver in $new_domain_
echo nameserver $nameserver >>/etc/resolv.conf
done
fi
chmod 644 /etc/resolv.conf
fi
}
Since it makes new_domain_ name_servers and new_domain_name independent.
Anyway, back to the point. Is there a reason why this bug has not been
fixed?