start hostname: hostname stop/waiting

Bug #662469 reported by Tong Sun

This bug report was converted into a question: question #134401: start hostname: hostname stop/waiting.

14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
hostname (Ubuntu)
Opinion
Undecided
Unassigned

Bug Description

Hi,

How to change hostname permanently without a reboot?

I've changed my /etc/hostname /etc/hosts, and want the system to reflect that.
In pure Debian, a /etc/init.d/hostname start will do, but in Ubuntu:

% /etc/init.d/hostname start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service hostname start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start hostname
hostname stop/waiting

% start hostname
hostname stop/waiting

What does this "hostname stop/waiting" mean here?
How to change hostname permanently without a reboot?

Thanks

PS Ubuntu 10.10 Maverick

Revision history for this message
Lorenzo De Liso (blackz) wrote :

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .

Changed in hostname (Ubuntu):
status: New → Invalid
Revision history for this message
Tong Sun (suntong001) wrote :

> If this "question" can't be answered in time, I'll convert it back to a bug report.

As I expected, a bug is a bug is a bug. A bug cannot be answered but solved.

Changed in hostname (Ubuntu):
status: Invalid → Opinion
Revision history for this message
Andrew (am-public-o) wrote :

I just created a new server instance running 14.04 and the same issue appeared.

Only way to resolve was a reboot.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.