public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: mku <matthias@kuntzem.de>
To: cygwin@cygwin.com
Subject: Re: commands spends time in cygheap_user
Date: Fri, 14 Aug 2015 13:49:00 -0000	[thread overview]
Message-ID: <1439560143628-120519.post@n5.nabble.com> (raw)
In-Reply-To: <20150812144754.GJ13029@calimero.vinschen.de>

I hope, not to follow a red herring again, but found some interesting.

I did a fresh cygwin installation again but made an error not to copy my old
.bashrc and .bashrc-profile files.
Within .bashrc I defined an alias for ls (ls='ls --color=auto
--show-control-chars').
I noticed, that the time lag has went away. After a "ls --color=auto", the
time lag appeared again.
Comparing the strace output with/without the color flag, I found that the
time lag at "cygheap_user::ontherange" has gone and it now appeared at a
ldap_bind [ldap_init] that was called in the context of a symbolic link to a
directory on a network share. The previous strace logs did not show a time
lag at this point, only at the cygheap_user entry. 

I deleted the "ln -s" entry and did not notice this big time lag any more
even with the color flag.

I restored the "old" v2.2.0 version and cannot find the previous logged time
lag. 
As no files within the cygwin directory structure has been modified, it
seems, that some registry information has been "healed" by the multiple
fresh installations. 

PS: To do a fresh install I did a "backup" by renaming the original cygwin
folder. The "restore" was done by renaming the fresh installed cygwin folder
and renaming the previous "backuped" folder back to cygwin.

For me the issue is now closed. Thanks for your input.

Regards, Matthias



--
View this message in context: http://cygwin.1069669.n5.nabble.com/commands-spends-time-in-cygheap-user-tp119766p120519.html
Sent from the Cygwin list mailing list archive at Nabble.com.

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

  reply	other threads:[~2015-08-14 13:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  6:26 pen
2015-08-07  8:48 ` mku
2015-08-07  9:06   ` Corinna Vinschen
2015-08-07 19:51     ` mku
2015-08-10  8:40       ` Corinna Vinschen
2015-08-10 12:00         ` mku
2015-08-10 16:01           ` Corinna Vinschen
2015-08-12 11:59             ` mku
2015-08-12 14:47               ` Corinna Vinschen
2015-08-14 13:49                 ` mku [this message]
2015-08-14 15:48                   ` Corinna Vinschen
2015-08-14 20:20                     ` Corinna Vinschen
2015-08-15 11:54                       ` Corinna Vinschen
2015-08-16 12:50                         ` mku
2015-08-17  8:07                           ` Corinna Vinschen
2015-08-17  8:13                             ` Corinna Vinschen
2015-08-17 10:10                               ` mku
2015-08-17 20:55                               ` Corinna Vinschen
2015-08-17 21:04                                 ` Corinna Vinschen
2015-08-18  8:17                                   ` mku
2015-08-18  8:30                                     ` Corinna Vinschen
2015-08-14 13:49             ` Corinna Vinschen

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=1439560143628-120519.post@n5.nabble.com \
    --to=matthias@kuntzem.de \
    --cc=cygwin@cygwin.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).