Re: Re: localhost.localdomain

2015-11-28 3:25 GMT-02:00 Crystal Wood : > ;) You shutdow use Bottom-posting [0]. :-) 0 - http://idallen.com/topposting.html Albino

Re: Re: localhost.localdomain

;)

Re: localhost.localdomain

Gabor Gombas [EMAIL PROTECTED] writes: On Fri, Oct 07, 2005 at 11:18:57AM -0700, Russ Allbery wrote: * Obtain the system host name with gethostname(). * Look up an IP address for that host with gethostbyname(). The bug is here. This is completely wrong but sadly very common practice. It

Re: localhost.localdomain

On Fri, Oct 07, 2005 at 11:18:57AM -0700, Russ Allbery wrote: * Obtain the system host name with gethostname(). * Look up an IP address for that host with gethostbyname(). The bug is here. This is completely wrong but sadly very common practice. It is common because it is portable and works

Re: localhost.localdomain

On Fri, Oct 07, 2005 at 04:15:18PM +0200, Christoph Haas wrote: MySQL definitely chokes on localhost.localdomain. And although MySQL will adopt to distributions using localhost.localdomain instead of localhost doesn't mean it's correct. MySQL by default expects localhost as the hostname

Re: localhost.localdomain

On Thu, Oct 13, 2005 at 12:35:11PM -0700, Jeff Stevens wrote: 1 -- When configuring DNS, 127.0.0.1 must resolve to localhost and vice versa [1]. No, the RFC does not say must, it only says should (and it is not even a SHOULD). And regardless if localhost.localdomain is removed from /etc/hosts

Re: localhost.localdomain

On 10/20/05, Gabor Gombas [EMAIL PROTECTED] wrote: The proper fix would be to enumerate all IP addresses of all network interfaces and select one that has an appropriate name. Unfortunately this is non-trivial and highly OS-dependent, although the libdumbnet1 package provides a

Re: localhost.localdomain

On Thu, Oct 20, 2005 at 04:16:40PM +0200, Olaf van der Spek wrote: Wouldn't the proper fix be to not use source address based authentication? This is not authentication. INN just need a string to uniquely identify a host. Using a FQDN is OK, it's just the way of obtaining that FQDN that is

Re: localhost.localdomain

On 10/20/05, Gabor Gombas [EMAIL PROTECTED] wrote: On Thu, Oct 20, 2005 at 04:16:40PM +0200, Olaf van der Spek wrote: Wouldn't the proper fix be to not use source address based authentication? This is not authentication. INN just need a string to uniquely identify a host. Using a FQDN is

Re: localhost.localdomain

On Fri, Oct 14, 2005 at 03:25:53AM -0500, Peter Samuelson wrote: Well, that's not quite true. As someone else pointed out earlier, AIX lists loopback localhost. On a fresh OpenBSD 3.7 install: ::1 localhost.home localhost 127.0.0.1 localhost.home localhost (home is the domain used on my

Re: localhost.localdomain

On Thursday 20 October 2005 16:01, Gabor Gombas wrote: On Fri, Oct 07, 2005 at 04:15:18PM +0200, Christoph Haas wrote: MySQL definitely chokes on localhost.localdomain. And although MySQL will adopt to distributions using localhost.localdomain instead of localhost doesn't mean it's correct.

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Do den 20. Okt 2005 um 16:01 schrieb Gabor Gombas: No, MySQL is happy to use whatever name the loopback interface has; it is the MySQL _documentation_ that stresses the localhost string without mentioning that it depends on the naming service

Re: localhost.localdomain

Gabor Gombas [EMAIL PROTECTED] writes: On a fresh OpenBSD 3.7 install: ::1 localhost.home localhost 127.0.0.1 localhost.home localhost Heh, I'm just surprised it's not: 127.0.0.1 OpenLocalHOST localhost -miles -- Quidquid latine dictum sit, altum viditur. -- To UNSUBSCRIBE, email to

Re: localhost.localdomain

[Jeff Stevens] If /etc/hosts were changed to: 127.0.0.1 localhost localhost.localdomain Resolution of 127.0.0.1 would properly return localhost. Yeah, but that's all beside the point. There is no point in swapping the order of the two names unless there be any point in having

Re: localhost.localdomain

OK, I have modified netcfg so that it writes 127.0.0.1 localhost to /etc/hosts. From now on let's consider at least the following two phenomena to be bugs: * The application expects to be able to resolve 'localhost.localdomain' to an IP address. * The application breaks if

Re: localhost.localdomain

On Friday 14 October 2005 02:47, Thomas Hood wrote: OK, I have modified netcfg so that it writes 127.0.0.1 localhost to /etc/hosts. Thank you! Yay for purging ugly non-standardness! =) From now on let's consider at least the following two phenomena to be bugs: * The application

Re: localhost.localdomain

On Fri, 2005-10-14 at 10:47 +0200, Thomas Hood wrote: OK, I have modified netcfg so that it writes 127.0.0.1 localhost to /etc/hosts. From now on let's consider at least the following two phenomena to be bugs: * The application expects to be able to resolve

Re: localhost.localdomain

Thomas... On Friday 14 October 2005 10:47, Thomas Hood wrote: OK, I have modified netcfg so that it writes 127.0.0.1 localhost to /etc/hosts. Thank you very much. My fellow sysadmins will appreciate that. And of course I'm very glad that after a lot of global warming the thread finally

Re: localhost.localdomain

Thomas Hood wrote: OK, I have modified netcfg so that it writes 127.0.0.1localhost to /etc/hosts. Excellent. Thank you. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: localhost.localdomain

The change from 'localhost' to 'localhost.localdomain' was made in svn revision 16759. The Debian changelog entry added at that time refers to bug report #247734. Looking at #247734 I see that 'localhost.localdomain' appeared without anyone either supporting its inclusion or objecting to it.

Re: localhost.localdomain

On Thu, 2005-10-13 at 16:02 +0200, Thomas Hood wrote: The change from 'localhost' to 'localhost.localdomain' was made in svn revision 16759. The Debian changelog entry added at that time refers to bug report #247734. Looking at #247734 I see that 'localhost.localdomain' appeared without

Re: localhost.localdomain

[Joey Hess] So far, this thread has not yeilded anything I can trust to that degree. [Christoph Haas] IIRC it yielded the fact that localhost.localdomain is has been added to fix applications Not that I've noticed. Maybe I just missed it, but *what* applications or *what* problems does

Re: localhost.localdomain

On Sat, 2005-10-08 at 23:04 +0200, Frans Pop wrote: On Saturday 08 October 2005 22:07, Jeff Stevens wrote: On Fri, 2005-10-07 at 16:26 +0200, Christoph Haas wrote: localhost.localdomain and localhost must be swapped. The first entry in the list of hosts *must* be localhost. You make

Re: localhost.localdomain

On Sat, Oct 08, 2005 at 06:53:28PM -0400, Joey Hess wrote: But it's then very hard to see if this breaks anything. After all, the relevant change was made in netcfg in July of 2004. For an entire year, it was in every system installed, and nobody complained, although a few of us noticed it and

Re: localhost.localdomain

On Fri, 2005-10-07 at 16:26 +0200, Christoph Haas wrote: The problem is probably that the localhost.localdomain stands before localhost in that line. So if you reverse resolve 127.0.0.1 you end up with localhost.localdomain which some applications don't understand. Christopher hits the nail

Re: localhost.localdomain

Jeff Stevens [EMAIL PROTECTED] writes: I don't have access to AIX, HPUX or other major Unices, but I bet in the hosts file, 127.0.0.1 is immediately followed by localhost -- and other aliases follow localhost. localhost *must* be first. AIX 5.2: 127.0.0.1 loopback localhost HP-UX 11.00:

Re: localhost.localdomain

On Saturday 08 October 2005 22:07, Jeff Stevens wrote: On Fri, 2005-10-07 at 16:26 +0200, Christoph Haas wrote: localhost.localdomain and localhost must be swapped. The first entry in the list of hosts *must* be localhost. You make quite a lot of noise it this mail, but I fail to find any

Re: localhost.localdomain

Klaus Ethgen wrote: The only reason I find is that RedHat use it. But RedHat shouldn't be debians requirement of quality. It should be other way around. RedHat is such a buggy distribution. And it gets more and more worse every upgrade. Klaus Ethgen wrote: But why changing localhost to

Re: localhost.localdomain

Henrique de Moraes Holschuh wrote: I read that bug report VERY carefully. Twice. There is *nothing* there that seems to have been fixed/addressed by .localdomain, except maybe a DNS timeout in Pierre's machine. Everything else deals with the hostname. I don't have the stamina that you do, so

Re: localhost.localdomain

On Oct 08, Frans Pop [EMAIL PROTECTED] wrote: You give nice explanations how things work, but fail to say anywhere why having localhost.localdomain first is so wrong. What breaks? What standards (with reference please) are not honored? An obvious problem is that gethostbyaddr and DNS queries

Re: localhost.localdomain

Gabor Gombas wrote: Then fix those other broken things as well. Contrary to popular belief among our users, system administrators does not have access to every server on the internet. Therefore, I can not help you solve this issue in this way. Instead, I propose we return the content of

Re: localhost.localdomain

On Sat, Oct 08, 2005 at 11:04:09PM +0200, Frans Pop wrote: On Saturday 08 October 2005 22:07, Jeff Stevens wrote: localhost.localdomain and localhost must be swapped. The first entry in the list of hosts *must* be localhost. You make quite a lot of noise it this mail, but I fail to find

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 03:25:15PM +0200, Gabor Gombas wrote: On Thu, Oct 06, 2005 at 07:31:37AM -0500, Steve Greenland wrote: When proposing a variation from long-standing historical practice, shouldn't the onus be on the on making the change? What problem does 'localhost.localdomain' solve?

Re: localhost.localdomain

On Fri, Oct 07, 2005 at 08:12:38AM +0200, Lionel Elie Mamane wrote: Having the DNS and /etc/hosts give different results is asking for trouble. RFC 1912 says that this discussion was had in the past and the conclusion was localhost.. Note that that discussion was about appending the local

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 12:44:34PM -0700, Russ Allbery wrote: No, they won't, because INN ignores hostnames that do not contain a period for the purposes of generating external identifiers, specifically to keep from using things like localhost or other unqualified names that aren't globally

Re: localhost.localdomain

On Fri, Oct 07, 2005 at 04:45:24AM +0200, Bernd Eckenfels wrote: Those asumptions are not false, they are what they are: asumptions. If you dont want to configure your system that way, just dont use it. That is what I say: every Debian package that uses hostname -f is bogus, because it relies

Re: localhost.localdomain

On Fri, Oct 07, 2005 at 07:10:07AM +0200, Stig Sandbeck Mathisen wrote: Changing the canonical name of localhost is an arbitrary change that breaks more than MySQL. It also violates the principle of least astonishment. Then fix those other broken things as well. If you want localhost-style

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 12:37:47PM +0200, Marco d'Itri wrote: On Oct 06, Klaus Ethgen [EMAIL PROTECTED] wrote: .localdomain is such a peace of shit which only makes troubles. So Please explain which troubles. Mine with MySQL. And the reason why I initiated this thread. :) MySQL definitely

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 07:44:42PM +0200, Pierre Machard wrote: Hi, On Thu, Oct 06, 2005 at 12:24:12PM -0300, Henrique de Moraes Holschuh wrote: On Thu, 06 Oct 2005, Pierre Machard wrote: IIRC The main reason was described in #247734 ARGH! If that bug was the reason why the

Re: localhost.localdomain

On Fri, Oct 07, 2005 at 02:04:44PM +0200, Gabor Gombas wrote: That is what I say: every Debian package that uses hostname -f is bogus, because it relies on a certain system configuration. Umm, I guess all debian packages relies on certain configurations. Gruss Bernd -- To UNSUBSCRIBE, email

Re: localhost.localdomain

Gabor Gombas [EMAIL PROTECTED] writes: Hmm, how would INN react if it sees a normal-looking name (like foo.bar.com) that in turn resolves to 127.0.0.1? It's been a long time since I last run a news server and I used Diablo instead of INN so I'm not familiar with INN's internals. But it seems

Re: localhost.localdomain

On Sat, Sep 24, 2005 at 08:33:25PM +0200, Bernd Eckenfels wrote: In article [EMAIL PROTECTED] you wrote: localdomain is not a registered top-level domain and hopefully never will be, so it is safe to use locally as it won't cause communication problems. It is not safe to use unregistered

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am Do den 6. Okt 2005 um 9:10 schrieb Pierre Machard: IIRC The main reason was described in #247734 The only reason I find is that RedHat use it. But RedHat shouldn't be debians requirement of quality. It should be other way around. RedHat is

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 06, Klaus Ethgen [EMAIL PROTECTED] wrote: .localdomain is such a peace of shit which only makes troubles. So Please explain which troubles. - -- ciao, Marco -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux)

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Marco, Am Do den 6. Okt 2005 um 12:37 schrieb Marco d'Itri: .localdomain is such a peace of shit which only makes troubles. So Please explain which troubles. I cannot specify it. But I remember that I did search for problemes in the past

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 06, Klaus Ethgen [EMAIL PROTECTED] wrote: Am Do den 6. Okt 2005 um 12:37 schrieb Marco d'Itri: .localdomain is such a peace of shit which only makes troubles. So Please explain which troubles. I cannot specify it. But I remember that I

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Marco, unfortunality your mail address is not valid so I answer you here. Am Do den 6. Okt 2005 um 13:48 schrieb Marco d'Itri: In other words, you don't know and are just handwaving. Next? No, I just do not remember which software it was. I

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 06, Klaus Ethgen [EMAIL PROTECTED] wrote: unfortunality your mail address is not valid so I answer you here. My email address is perfectly valid, it's your system which is misconfigured: Oct 6 13:42:11 picard postfix/smtpd[4344]: NOQUEUE:

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 02:04:44PM +0200, Klaus Ethgen wrote: Hi Marco, unfortunality your mail address is not valid so I answer you here. Am Do den 6. Okt 2005 um 13:48 schrieb Marco d'Itri: In other words, you don't know and are just handwaving. Next? No, I just do not remember

Re: localhost.localdomain

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Am Do den 6. Okt 2005 um 14:22 schrieb Wouter Verhelst: That's not helpful. True. Thats the reason why I give more helpfull information too in the first mail. indeed cause many problems, we could consider not using it by default anymore.

Re: localhost.localdomain

On 06-Oct-05, 07:22 (CDT), Wouter Verhelst [EMAIL PROTECTED] wrote: On Thu, Oct 06, 2005 at 02:04:44PM +0200, Klaus Ethgen wrote: Problems can have many causes. One of them may be that localhost.localdomain is unexpected; another may be that the software you were using is buggy, or

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 01:43:29PM +0200, Klaus Ethgen wrote: I cannot specify it. But I remember that I did search for problemes in the past long time to find a error. And it was an entry of localhost.localdomain in a /etc/hosts. Maybe it was PVM or MySQL or other. I'm not sure. IIRC

Re: localhost.localdomain

Klaus Ethgen writes: Thats the reason why I give more helpfull information too in the first mail. You haven't given enough information. But why changing localhost to localhost.localdomain... It wasn't changed. localhost.localdomain was _added_. localhost is still there. There was

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 07:31:37AM -0500, Steve Greenland wrote: When proposing a variation from long-standing historical practice, shouldn't the onus be on the on making the change? What problem does 'localhost.localdomain' solve? Why is is better than just 'localhost', which has been common

Re: localhost.localdomain

On Thu, 06 Oct 2005, Marco d'Itri wrote: On Oct 06, Klaus Ethgen [EMAIL PROTECTED] wrote: .localdomain is such a peace of shit which only makes troubles. So Please explain which troubles. Some programs will try to solve the reverse for 127.0.0.1, during normal operations (not to verify WHAT

Re: localhost.localdomain

On Thu, 06 Oct 2005, Gabor Gombas wrote: It's being long-standing does not mean it's correct. I started looking But it means it is a de-facto standard, which it *is*. Every *nix system I have mucked around with in the last five years, with the exception of a few Linux distributions, uses plain

Re: localhost.localdomain

On Thu, 06 Oct 2005, John Hasler wrote: But why changing localhost to localhost.localdomain... It wasn't changed. localhost.localdomain was _added_. localhost is still there. The first entry is the canonical name, and it is what the reverse maps to. So yes, it WAS changed, and very much

Re: localhost.localdomain

On 06-Oct-05, 08:25 (CDT), Gabor Gombas [EMAIL PROTECTED] wrote: It's being long-standing does not mean it's correct. No, but it doesn't make changing it correct, either. Again: what actual technical problem is solved by 'localhost.localdomain? Is solving that problem worth the potential

Re: localhost.localdomain

I wrote: It wasn't changed. localhost.localdomain was _added_. localhost is still there. Henrique de Moraes Holschuh writes: The first entry is the canonical name, and it is what the reverse maps to. So yes, it WAS changed, and very much so. The OP seemed to me to be implying that

Re: localhost.localdomain

On Thu, 06 Oct 2005, Pierre Machard wrote: On Sat, Sep 24, 2005 at 08:33:25PM +0200, Bernd Eckenfels wrote: In article [EMAIL PROTECTED] you wrote: localdomain is not a registered top-level domain and hopefully never will be, so it is safe to use locally as it won't cause communication

Re: localhost.localdomain

On Thu, 06 Oct 2005, John Hasler wrote: Read the discussion in the bug report. I think localhost.localdomain is I did. localhost.localdomain solved no problems, it was not even related to the problem they were trying to fix, and it certainly is not part of the best compromise solution (add

Re: localhost.localdomain

Hi, On Thu, Oct 06, 2005 at 12:24:12PM -0300, Henrique de Moraes Holschuh wrote: On Thu, 06 Oct 2005, Pierre Machard wrote: On Sat, Sep 24, 2005 at 08:33:25PM +0200, Bernd Eckenfels wrote: In article [EMAIL PROTECTED] you wrote: localdomain is not a registered top-level domain and

Re: localhost.localdomain

Marco d'Itri [EMAIL PROTECTED] writes: On Oct 06, Klaus Ethgen [EMAIL PROTECTED] wrote: .localdomain is such a peace of shit which only makes troubles. So Please explain which troubles. See the news.software.nntp traffic with people having strange problems with pathnames and message ID

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 07:44:42PM +0200, Pierre Machard wrote: I can not remember precisely. I think that at that time I was testing the debian-installer and I saw it was taken a long while to boot. I saw that my system had no FQDN (hostname -f). When you add .localdomain, the FQDN is

Re: localhost.localdomain

On Thu, 06 Oct 2005, Pierre Machard wrote: Anyway I do not understand why this issue is a problem since we Because instead of doing this: 127.0.0.1 localost localhost.localdomain It was done like this: 127.0.0.1 localhost.localdomain localhost Thus changing the canonical name of the loopback

Re: localhost.localdomain

On Oct 06, Russ Allbery [EMAIL PROTECTED] wrote: See the news.software.nntp traffic with people having strange problems with pathnames and message ID generation because of .localdomain. There have been a few separate cases of that over the past year or so. Not relevant. They would have the

Re: localhost.localdomain

On Oct 06, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: Because instead of doing this: 127.0.0.1 localost localhost.localdomain It was done like this: 127.0.0.1 localhost.localdomain localhost Thus changing the canonical name of the loopback interface. PLEASE do not do this

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 03:23:45PM -0300, Henrique de Moraes Holschuh wrote: On Thu, 06 Oct 2005, Pierre Machard wrote: Anyway I do not understand why this issue is a problem since we Because instead of doing this: 127.0.0.1 localost localhost.localdomain It was done like this:

Re: localhost.localdomain

In article [EMAIL PROTECTED] you wrote: I can not remember precisely. I think that at that time I was testing the debian-installer and I saw it was taken a long while to boot. I saw that my system had no FQDN (hostname -f). When you add .localdomain, the FQDN is complete and it helps to solve

Re: localhost.localdomain

Henrique de Moraes Holschuh wrote: Because instead of doing this: 127.0.0.1 localost localhost.localdomain It was done like this: 127.0.0.1 localhost.localdomain localhost Thus changing the canonical name of the loopback interface. PLEASE do not do this unless you have *extremely*

Re: localhost.localdomain

Marco d'Itri [EMAIL PROTECTED] writes: On Oct 06, Russ Allbery [EMAIL PROTECTED] wrote: See the news.software.nntp traffic with people having strange problems with pathnames and message ID generation because of .localdomain. There have been a few separate cases of that over the past year or

Re: localhost.localdomain

On Thu, 06 Oct 2005, Pierre Machard wrote: The fact is that nobody complained about that... and my bug was Now we are :) repported more than one year and a half ago. Plus It was disscussed on debian-devel. Please do not argue with me! It is nothing personal... it is just that your email was

Re: localhost.localdomain

On Thu, 06 Oct 2005, Joey Hess wrote: FWIW, it was done as a result of bug #247734, which includes details on how every possible choice seems to break something and the reasoning that led to the current choice. I read that bug report VERY carefully. Twice. There is *nothing* there that seems

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 03:17:53PM +0200, Stefano Zacchiroli wrote: IIRC leafnode complains about localhost.localdomain refusing to suck news unless you manually specify a domainname in its configuration file. Maybe you remember that trouble? Still, I've ever considered that an issue with

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 09:38:03PM +0100, Mark Brown wrote: It's complaining because upstream wishes to strongly encourage users to configure things so that they have a globally unique hostname part to message IDs that are generated by Leafnode in order to minimise the risk IMHO is too much to

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 05:02:55PM -0300, Henrique de Moraes Holschuh wrote: Or am I getting confused and d-i uses localhost.localdomain as the default hostname, and say, if I had told it that my machine is named twerk, domain foo.bar I would get a 127.0.0.1 twerk.foo.bar twerk localhost

Re: localhost.localdomain

On Thu, Oct 06, 2005 at 10:41:13PM +0200, Stefano Zacchiroli wrote: On Thu, Oct 06, 2005 at 09:38:03PM +0100, Mark Brown wrote: It's complaining because upstream wishes to strongly encourage users to configure things so that they have a globally unique hostname part to message IDs that are

Re: localhost.localdomain

Russ Allbery writes: No, they won't, because INN ignores hostnames that do not contain a period for the purposes of generating external identifiers, specifically to keep from using things like localhost or other unqualified names that aren't globally unique. Relying on hostnames either with

Re: localhost.localdomain

Stefano Zacchiroli writes: IMHO is too much to inhibit the use of the program as a whole just to minimize the collision risk, a warning would have been enough. Particularly considering that there are better ways to assure the uniqueness of message-ids anyway. -- John Hasler -- To

Re: localhost.localdomain

John Hasler [EMAIL PROTECTED] writes: Russ Allbery writes: No, they won't, because INN ignores hostnames that do not contain a period for the purposes of generating external identifiers, specifically to keep from using things like localhost or other unqualified names that aren't globally

Re: localhost.localdomain

On Thursday 06 October 2005 14:02, Henrique de Moraes Holschuh wrote: On Thu, 06 Oct 2005, Joey Hess wrote: FWIW, it was done as a result of bug #247734, which includes details on how every possible choice seems to break something and the reasoning that led to the current choice. I read

Re: localhost.localdomain

In article [EMAIL PROTECTED] you wrote: So it was just papering over a real bug, namely the existence of the -f option of hostname. hostname -f assumes that the hostname (as returned by gethostname(3)) has something to do with networking, which is false. It also assumes that the system has

Re: localhost.localdomain

Gabor Gombas [EMAIL PROTECTED] 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

Re: localhost.localdomain

Pierre Machard [EMAIL PROTECTED] writes: Anyway I do not understand why this issue is a problem since we simply add an alias to localhost. Nobody say that we will remove localhost and exchange it by localhost.localdomain. If what you wanted to do was to add an alias, you should have read the

Re: localhost.localdomain

Christoph Haas wrote: Actually I second that. I still haven't seen a reason to use it since I don't understand the historical reasons. I have always wondered about the historical reasons too. Because it never made sense to me either. On my servers I have always removed the

Re: localhost.localdomain

On Fri, Sep 23, 2005 at 08:01:05PM +0200, Christoph Haas wrote: It appears like MySQL does that. It seems to check the IP address of the connecting client to find the permissions in it's internal `users` table. So it sees 127.0.0.1 and looks up localhost.localdomain which it cannot find since

Re: localhost.localdomain

On Sat, Sep 24, 2005 at 07:35:09PM +0200, Gabor Gombas wrote: On Fri, Sep 23, 2005 at 08:01:05PM +0200, Christoph Haas wrote: It appears like MySQL does that. It seems to check the IP address of the connecting client to find the permissions in it's internal `users` table. So it sees

Re: localhost.localdomain

In article [EMAIL PROTECTED] you wrote: localdomain is not a registered top-level domain and hopefully never will be, so it is safe to use locally as it won't cause communication problems. It is not safe to use unregistered domains. and I dont see a reason for .localdmain at all. Gruss Bernd

Re: localhost.localdomain

Christoph Haas [EMAIL PROTECTED] writes: That's exactly the explanation what I was looking for. I incorrectly assumed that more than just MySQL is affected. But it appears like other services do not care about the reverse resolution of 127.0.0.1. This is also the case for CUPS, but is now

Re: localhost.localdomain

On Sat, 24 Sep 2005 19:35:09 +0200, Gabor Gombas wrote: [...] localdomain is not a registered top-level domain and hopefully never will be, so it is safe to use locally as it won't cause communication problems. Maybe it's relatively safe, but I'd say that it's still safer to use the localhost

Re: localhost.localdomain

On Sat, Sep 24, 2005 at 08:33:25PM +0200, Bernd Eckenfels wrote: In article [EMAIL PROTECTED] you wrote: localdomain is not a registered top-level domain and hopefully never will be, so it is safe to use locally as it won't cause communication problems. It is not safe to use unregistered

Re: localhost.localdomain

Christoph Haas [EMAIL PROTECTED] writes: That's exactly the explanation what I was looking for. I incorrectly assumed that more than just MySQL is affected. But it appears like other services do not care about the reverse resolution of 127.0.0.1. I've never seen the dumb localhost.localdomain

Re: localhost.localdomain

On Fri, Sep 23, 2005 at 02:47:58PM +0200, Christoph Haas wrote: ..warning: connect to mysql server foobar: Access denied for user 'whoever'@'localhost.localdomain' (using password: YES) Well, I had seen several machines having 127.0.0.1 localhost.localdomain localhost in /etc/hosts and running

Re: localhost.localdomain

On Fri, Sep 23, 2005 at 04:59:52PM +0200, Gabor Gombas wrote: On Fri, Sep 23, 2005 at 02:47:58PM +0200, Christoph Haas wrote: ..warning: connect to mysql server foobar: Access denied for user 'whoever'@'localhost.localdomain' (using password: YES) Well, I had seen several machines having

Re: localhost.localdomain

On 9/23/05, Christoph Haas [EMAIL PROTECTED] wrote: On Fri, Sep 23, 2005 at 04:59:52PM +0200, Gabor Gombas wrote: On Fri, Sep 23, 2005 at 02:47:58PM +0200, Christoph Haas wrote: ..warning: connect to mysql server foobar: Access denied for user 'whoever'@'localhost.localdomain' (using

Re: localhost.localdomain

On Fri, Sep 23, 2005 at 08:07:54PM +0200, Olaf van der Spek wrote: On 9/23/05, Christoph Haas [EMAIL PROTECTED] wrote: It appears like MySQL does that. It seems to check the IP address of the connecting client to find the permissions in it's internal `users` table. So it sees 127.0.0.1 and

Re: localhost.localdomain

On 9/23/05, Christoph Haas [EMAIL PROTECTED] wrote: On Fri, Sep 23, 2005 at 08:07:54PM +0200, Olaf van der Spek wrote: On 9/23/05, Christoph Haas [EMAIL PROTECTED] wrote: It appears like MySQL does that. It seems to check the IP address of the connecting client to find the permissions in