Subject: | |
From: | |
Reply To: | |
Date: | Tue, 23 Jul 2013 20:53:57 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Tue, Jul 23, 2013 at 2:36 PM, Konstantin Olchanski
<[log in to unmask]> wrote:
> On Tue, Jul 23, 2013 at 09:32:34AM +0100, [log in to unmask] wrote:
>>
>> Slow Application start-up times.
>>
Is a "live CD" or "live DVD" as slow? It's a very handy test case!
>
> Obviously something changed somewhere to cause your problem.
Hmmmm.... Have you been renaming your system and playing with
/etc/hosts? On most hosts, the Fully Qualified Host Name(tm) is listed
both in /etc/sysconfig/network, and in /etc/hosts. And in /etc/hosts,
it's usually something like this:
127.0.0.1 myhost.mydomain myhost
localhost.localdomain localhost localhost4.localdomain localhost4
::1 myhost.mydomain myhost
localhost.localdomain localhost localhost6.localdomain localhost6
192.168.1.1 myhost.mydomain myhost
Having it listed in the loopbacks and the active network ports is a
source of endless network religious argument, and can contribute to
all sorts of hairiness. Personally, I like to list it this way:
127.0.0.1 localhost.localdomain localhost
localhost4.localdomain localhost4
127.1.1.1 myhost.mydomain myhost
::1 localhost.localdomain localhost
localhost6.localdomain localhost6
That puts it on the loopback, and keeps editing tools from mucking
with the critial normal loopback entries. I also persoanlly like to
turn off IPv6 entirely if it's not in active use, simply to avoid
confusion in my normally NAT'ed workaspaces. And lord, if you've been
doing something common and "clever" like mounting NFS or CIFS drives
at "/local" or "/mymountpoint", and they're listed as automatically
mounted in /etc/fstab, and they're only erratically available, you've
only your Linux educators to blame for not using the File System
Hiearchy and moving the mount point *down* a few directories.
Mount points at the top of "/" that are failing are a famous source of
production issues.
|
|
|