Bug#696805: Suggested fix to blank hostname bug

To: Jimmy Kaplowitz <jkaplowitz@google.com>, 696805@bugs.debian.org
Subject: Bug#696805: Suggested fix to blank hostname bug
From: Anders Ingemann <anders@ingemann.de>
Date: Wed, 29 Jan 2014 23:44:54 +0100
Message-id: <[🔎] CAMcOGXFgQwfY8OoWgF-QTKxkM0yqmLnohnHYp2Sn_Audm3krdw@mail.gmail.com>
Reply-to: Anders Ingemann <anders@ingemann.de>, 696805@bugs.debian.org
In-reply-to: <[🔎] CAJbdudU-2pOgMoJbKTz0=dRjESQy6V0JZZEFeqW3oi-W9AZ_tg@mail.gmail.com>
References: <[🔎] CAJbdudU-2pOgMoJbKTz0=dRjESQy6V0JZZEFeqW3oi-W9AZ_tg@mail.gmail.com>

On 29 January 2014 02:38, Jimmy Kaplowitz <jkaplowitz@google.com> wrote:

Set the hostname to localhost in build-debian-cloud. The standard set_hostname logic in /sbin/dhclient-script will override this just fine, but it should fix the log clutter.

- Jimmy

Good idea. I already do it for the vagrant plugin: https://github.com/andsens/build-debian-cloud/blob/WIP-python/plugins/vagrant/tasks.py#L51

It should probably just be refactored so that you can set it under "system" in the manifest.

Reply to:

References:
- Bug#696805: Suggested fix to blank hostname bug
  - From: Jimmy Kaplowitz <jkaplowitz@google.com>

Prev by Date: Bug#696805: Suggested fix to blank hostname bug
Next by Date: Re: Moving GCE scripts to Python
Previous by thread: Bug#696805: Suggested fix to blank hostname bug
Index(es):
- Date
- Thread