On Sun, Nov 20, 2011 at 12:22 AM, Andrew Pollock wrote:
>
> dhclient-script got some major overhauling in 4.2.2-1, and your patch is no
> longer applicable.
>
> Is the original bug still present in 4.2.2-1?
>
> regards
>
> Andrew
Andrew,
It does appear to work normally in 4.2.2-1 on Sid. Howev
Once the dhclient-script has been accepted I'll be opening a bug on the
"initscripts" package to ensure hostname.sh is updated. Was posting the
diff here to ensure the change needing to be made was noted with a fix.
-Tim
e)"
@@ -28,6 +28,9 @@
# And set it to 'localhost' if no setting was found
[ -z "$HOSTNAME" ] && HOSTNAME=localhost
+ # Or set to localhost if hostname is "(none)"
+ [ "$HOSTNAME" = "(none)" ] && HOSTNAME=localhost
+
[
uot; -a -n "$host_name" -a \
- "$host_name" != "$old_host_name" ]; then
-hostname "$new_host_name"
+ if [ ! -s /etc/hostname ]; then
+ # /etc/hostname > 0 set hostname
+ hostname "$new_host_name"
fi
if [ -n "$ol
dress" -a -n "$alias_ip_address" -a \
The hostname.sh issue isn't critical, but it's still a bit unsettling to
see init scripts unhappy at boot. I'll work on something for
"/etc/init.d/hostname.sh" so that it doesn't fail on boot. Things just
can't be easy, can they?
Tim Heckman
dhclient-script.diff
Description: Binary data
5 matches
Mail list logo
