Scott,
I just tested a recent Maverick AMI and it does indeed correctly set the
hostname to the newly assigned internal domain name after a stop/start
sequence. So no need to open any other bugs on that score.
+ uname -n
ip-10-117-39-235
+ hostname -s
ip-10-117-39-235
+ hostname -d
cloud-init does a lot of things. I guess what I'm looking for is
whether cloud-init could be made to emit events as it works such that
other upstart jobs can listen for those events and then use them to
trigger their startup as opposed to waiting for the entire cloud-init
process to complete.
This fix is needed for Lucid as well.
I have a clustered filesystem that fails because of this bug. It relies
upon the hostname value always being set correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
As the ec2 meta-data, local-hostname, returns the long form of hostname,
I would also propose that an enhancement that a new ec2 meta-data attribute be
added:
local-shortname
that would return the short version of hostname such as is returned from
'hostname -s' on a properly configured
When hostname is properly working on a system all of the following
commands should work as expected:
#uname -n
#hostname -a
#hostname -s
#hostname -d
#hostname -f
#hostname
Source: http://www.debianadmin.com/change-hostname-or-server-name-of-a
-linux-machine.html
--
You received this bug
Running the following commands appears to correctly set all the forms of
hostname on my Lucid ec2 instance:
echo $(curl -s http://169.254.169.254/latest/meta-data/local-hostname)
| sed 's:\..*$::' /etc/hostname
/sbin/sysctl -w kernel.hostname=$(curl -s http://169.254.169.254/latest
Now since my cluster filesystem starts real early in the bootup (S20) I
need the hostname to be set correctly even earlier.
So that would probably require some upstart job to run at S10.
So now I need to see how cloud-init is doing this and if it is early in
the bootup.
--
You received this
included the addition of -b. I don't know what
impact that has but it made sense when I was working on it.
Gerry
On Sat, 11 Dec 2010, Stéphane Graber wrote:
I can confirm that the fix works as expected, here's the output of my test.
I started a bash shell as tomcat6 in a shell, then ran
Here's my comment included as an attached patch. What does it take to
actually get this into a release?
** Patch added: Patch to add -p $CATALINA_PID to the initscript tomcat6 file
https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/632554/+attachment/1731835/+files/tomcat6.init.patch
I'm struck by this bug because I have the tomcat user doing something
else related to tomcat, so it MIGHT actually be logged in.
It strikes me as a bad idea to let a startup script create a file in
/etc/init.d/. We should find a better way to clarify that it's actually a
tomcat instance
The problem is fixed if we add `-p $CATALINA_PID` to the start-stop-daemon
line in catalina_sh(). Isn't that something we should be able to rely on?
{{{
*** tomcat6~2010-10-11 13:21:52.0 -0500
--- tomcat6 2010-11-03 12:19:04.0 -0500
***
*** 152,154
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) = Ubuntu Development Team (ubuntu-dev)
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) = Ubuntu Development Team (ubuntu-dev)
--
package update-manager 1:0.93.18 failed to install/upgrade: ErrorMessage:
SystemError
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
Please add nf_conntrack_pptp and nf_conntrack_netbios_ns to IPT_MODULES
https://bugs.launchpad.net/bugs/360975
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Ubuntu Development Team (ubuntu-dev)
--
Please add nf_conntrack_pptp and nf_conntrack_netbios_ns to IPT_MODULES
** Also affects: opensc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: opensc (Debian)
Importance: Undecided
Status: New
--
smartcard support is not enabled in openssh
https://bugs.launchpad.net/bugs/16918
You received this bug notification because you are a
this is fixed in the
latest available packages. I have performed apt-get update apt-get upgrade.
All packages are reported to be up to date.
Am I missing something?
Best Regards,
- Gerry
--
Segfaults in apache2 with libapache2-mod-php5 installed
https://bugs.launchpad.net/bugs/418897
You received
16 matches
Mail list logo
