From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: commands spends time in cygheap_user
Date: Fri, 14 Aug 2015 15:48:00 -0000 [thread overview]
Message-ID: <20150814154832.GK28349@calimero.vinschen.de> (raw)
In-Reply-To: <1439560143628-120519.post@n5.nabble.com>
[-- Attachment #1: Type: text/plain, Size: 1842 bytes --]
On Aug 14 06:49, mku wrote:
> 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.
Thank you for this important point. That gives me an idea what
happens and I guess this is something which needs fixing. These
checks should also only happen if passwd/group in nsswitch.conf
are set to "db".
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-14 15:48 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
2015-08-14 15:48 ` Corinna Vinschen [this message]
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=20150814154832.GK28349@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).