zsh-users
 help / color / mirror / code / Atom feed
From: Renato Botelho <rbgarga@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: Zsh startup really slow after upgrade to fedora 15 [SOLVED]
Date: Thu, 8 Sep 2011 16:56:49 -0300	[thread overview]
Message-ID: <CAESiWkn5m=NS4EDQZzrGg_NQ9hZY7aJrx3pjqzLXRzZZbXfuSg@mail.gmail.com> (raw)

On Mon, Sep 5, 2011 at 5:56 PM, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 5, 10:35pm, Mikael Magnusson wrote:
> }
> } We solved this on irc, it turned out to be that group lookup thing in
> } compaudit you fixed/worked around the other week
>
> Curious that upgrading to Fedora 15 would cause that.  I would expect
> it only to occur in a networked environment.  It is possible that F15
> has the networked version of getent enabled by default now, and the
> long delay is because it's waiting for a connection to a non-existent
> server to time out?

Like Mikael said, i added 'compinit -u' and it helped me a lot, but i
was still having a big delay on completion.

After dig into it i figured out my problem was being caused because
i had a symlink "/usr/bin/foo" that was pointing to a NFS mounted
directory, and it was the cause of delay. After remove this symlink
it started to work fine again even if i remove -u option from compinit.

The conclusion is it was just an environment problem, not zsh, sorry
for the noise.

And i figured out it started happening after i upgrade to fedora 15
because there is a local repository with tools from the company i
work for, and one of those packages created that link on my
/usr/bin.

Regards
-- 
Renato Botelho


             reply	other threads:[~2011-09-08 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 19:56 Renato Botelho [this message]
2011-09-08 21:24 ` Bart Schaefer
2011-09-09 19:59   ` Renato Botelho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAESiWkn5m=NS4EDQZzrGg_NQ9hZY7aJrx3pjqzLXRzZZbXfuSg@mail.gmail.com' \
    --to=rbgarga@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).