- To: email@example.com
- Subject: Re: localhost.localdomain
- From: Stig Sandbeck Mathisen <firstname.lastname@example.org>
- Date: Fri, 07 Oct 2005 07:10:07 +0200
- Message-id: <[🔎] email@example.com>
- In-reply-to: <20050924173508.GG29334@boogie.lpds.sztaki.hu> (Gabor Gombas's message of "Sat, 24 Sep 2005 19:35:09 +0200")
- References: <20050923124758.GA3104@torf.workaround.org> <20050923145947.GE22420@boogie.lpds.sztaki.hu> <20050923180105.GA21570@torf.workaround.org> <20050924173508.GG29334@boogie.lpds.sztaki.hu>
Gabor Gombas <firstname.lastname@example.org> writes:
> Ok, after a quick googling I found that this bug has already been
> reported for MySQL: http://bugs.mysql.com/11822 and is fixed in
> MySQL 5.0.11. So if it bothers you, you should upgrade.
Changing the canonical name of localhost is an arbitrary change that
breaks more than MySQL. It also violates the principle of least
"We've changed something, we're not sure why, but it breaks MySQL.
If it bothers you, you should upgrade MySQL"
Nah, I don't think that is what we want to tell our users.
Stig Sandbeck Mathisen