From: Eric Raible <raible@gmail.com>
Date: Tue, 10 Feb 2009 11:39:11 GMT
Subject: Re: RFH: spawning pager takes long time when when unconnected from network
Message-ID: <279b37b20902100339w6e4d215cua41887c65f7c37bc@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0902101159300.10279@pacific.mpi-cbg.de>

On Tue, Feb 10, 2009 at 3:03 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> You could also try to set it to /bin/false, just so you know if the delay
> is caused by the shell startup.
>
> In my experience, such intermittent delays are often triggered by some
> (mostly unnecessary) calls to either DNS (which might hang for quite some
> time) or domain controllers (same).  These can be triggered by shell
> startup looking for the user or host name.
>
> However, I am just fishing here, as I cannot begin to get an idea what is
> happening on your side.
>
> Also, it does not help that the platform is Windows, an OS I am mostly
> unfamiliar with.  But there have to be profiling tools for that platform
> where you should be able to see what function is blocking (I assume it is
> a blocking call, of course).
>
> Ciao,
> Dscho

Toggling core.pager btwn /bin/false and less is slow the first time,
then quick subsequent times.  Setting core.pager to "echo no pager"
gives the same behavior.

What would be handy is a windows version of strace, but the one
that I found doesn't seem functional.  gdb is useless for this
(so far, anyway).    I think it's time to sleep on this.

Thanks - Eric