This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Waiting for //.terminfo or //.termcap


Igor Peshansky <pechtcha@cs.nyu.edu> wrote on 03/28/2007 12:39:15 PM:

> On Wed, 28 Mar 2007, Ken Fast wrote:
>
> > Opening a bash shell has been much slower lately.  (New WinXP machine,
> > or new cygwin install?)  Also, using some simple commands like man is
> > terribly slow.  In looking through the strace logs for bash, less (the
> > slow part of man pages), and more (tried as an alternative to less for
> > man pages) I see a 6 or 7 second delay for a search for //.terminfo or
> > //.termcap.  I am on a network connected machine in a corporate
setting,
> > so there are a lot of entries at //.  A simple ls // comes back in a
> > second or two, but searching for //.terminfo is killing me.  My TERM
> > environment variable is set to cygwin.  Why doesn't cygwin look in
> > C:/cygwin/usr/share/terminfo/c/cygwin first instead of looking across
> > the entire network for .terminfo?
> >
> > Note: I posted yesterday on another thread about the DLA problem.  I
> > think it may not be a DLA issue at all, unless DLA is causing this
> > global search for terminfo.
> >


>
> You didn't attach the output of "cygcheck -svr", as requested in
>
> > Problem reports:       http://cygwin.com/problems.html
>
> so I have to ask: what is your HOME set to?  If it's set to "/", that
> would explain the behavior (although it's arguably a bug in ncurses,
since
> it should be looking for /.terminfo instead).  Try setting your HOME to
> something else.  And please follow the above "Problem reports" link and
> provide the requested information.
>    Igor
> --
>             http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_       pechtcha@cs.nyu.edu | igor@watson.ibm.com
> ZZZzz /,`.-'`'    -.  ;-;;,_      Igor Peshansky, Ph.D. (name changed!)
>      |,4-  ) )-,_. ,\ (  `'-'      old name: Igor Pechtchanski
>     '---''(_/--'  `-'\_) fL   a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>
> Freedom is just another word for "nothing left to lose"...  -- Janis
Joplin

(See attached file: cygcheck.txt)

Yes, my HOME was set to "/".  I set it to something else and that fixed the
speed problem.
However, in my Windows profile HOME is actually set to "C:/cygwin".  It is
the mount of
C:/cygwin on / that resets it to "/".  How do I keep HOME pointing to
"C:/cygwin" instead
of "/", or do I need HOME set at all?  Should I keep HOME out of my Windows
profile and
just put it in .bashrc instead?

As for the bug in ncurses, is this a known thing, or a useful thing to
pursue?

Ken

Attachment: cygcheck.txt
Description: Binary data

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]