Message from discussion Debian Squeeze AMI hostname.sh
Received: by 10.42.76.197 with SMTP id f5mr140405ick.3.1331845806751;
Thu, 15 Mar 2012 14:10:06 -0700 (PDT)
Received: by 10.220.208.93 with SMTP id gb29ls1972799vcb.2.gmail; Thu, 15 Mar
2012 14:10:05 -0700 (PDT)
Received: by 10.52.37.101 with SMTP id x5mr50948vdj.4.1331845805436; Thu, 15
Mar 2012 14:10:05 -0700 (PDT)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
ands...@gmail.com designates internal as permitted sender)
Received: by q11g2000vbu.googlegroups.com with HTTP; Thu, 15 Mar 2012 14:10:05
Date: Thu, 15 Mar 2012 14:10:05 -0700 (PDT)
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3)
AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.79 Safari/535.11,gzip(gfe)
Subject: Re: Debian Squeeze AMI hostname.sh
From: andsens <ands...@gmail.com>
To: ec2debian <firstname.lastname@example.org>
Content-Type: text/plain; charset=ISO-8859-1
Well its not really the purpose of the script to be dependent on NICs.
It's only purpose is to set the hostname in the kernel to what is
defined in /etc/hostname.
Later on DHCP clients might change that, but that change does not need
to go through hostname.sh
On Mar 15, 9:08=A0pm, Josh Kraemer <joshkrae...@gmail.com> wrote:
> It seems this issue is related to the fact that hostname.sh is run before
> the network interfaces are configured.
> On Wednesday, March 14, 2012 4:52:43 AM UTC-5, andsens wrote:
> > I have a made a buildscript where I took care of every possible
> > startup error. But I gave up on hostname.sh.
> > There is a bug when the hostname is not set in '/etc/hostname' (or
> > because it has not been assigned by DHCP yet).
> > hostname.sh is supposed to set it to localhost. The problem with all
> > that is that `hostname` returns '(none)' instead of an empty string in
> > this case.
> > The script does not account for that, and tries to set it to '(none)'
> > instead, which is an invalid hostname.
> > I would suggest ignoring it, until the bug is fixed.
> > On Mar 13, 11:21 pm, Josh Kraemer <joshkrae...@gmail.com> wrote:
> > > I'm using a Debian AMI that I built from scratch. Whether I use my ow=
> > > Debian AMI or an existing published Debian AMI, I always notice the
> > > following errors from the system console log when the instance boots:
> > > hostname: the specified hostname is invalid
> > > startpar: service(s) returned failure: hostname.sh ...
> > > hostname.sh is an init.d script that Debian uses to set the hostname
> > from
> > > /etc/hostname, which doesn't exist and is not used in any Debian AMIs=
> > > How can I disable or remove hostname.sh? I've tried to remove it, but
> > then
> > > I just get errors that hostname.sh could not be found, because it's
> > > symlinked from somewhere else.
> > > The above errors don't affect the operation of the instance, but it's
> > just