Cygwin used to run very quickly for me; now it doesn't. Not sure when it
stopped -- last few weeks.
# time for i in {1..5} ; do bash -c "echo Hello" ; done
Hello
Hello
Hello
Hello
Hello
real0m51.451s
user0m0.230s
sys 0m0.979s
# time ls | wc -l
21
real0m10.231s
user0m0.030s
On 9/30/2012 10:43 PM, Adam Rosi-Kessel wrote:
Cygwin used to run very quickly for me; now it doesn't. Not sure when it
stopped -- last few weeks.
# time for i in {1..5} ; do bash -c "echo Hello" ; done
Hello
Hello
Hello
Hello
Hello
real0m51.451s
user0m0.230s
sys 0m0.979s
much le
On 2012-10-01 AM 5:43, Adam Rosi-Kessel wrote:
22 10401 [main] ls 24012 cygheap_user::ontherange: Set HOME (from
/etc/passwd) to /cygdrive/c/0/cygwin_home
100 10501 [main] ls 24012 normalize_posix_path: src
/cygdrive/c/0/cygwin_home
40 10541 [main] ls 24012 normalize_posix_path:
On Mon, Oct 1, 2012 at 9:33 AM, jojelino wrote:
> if the SkyDrive is trademark of M$ and if it needs network connection to
> remote server, it would piss you off like you have been experienced.
> If it is the case, please stop using *Skydrive* mounted directory as home
> directory for specific u
On Sun, Sep 30, 2012 at 4:43 PM, Adam Rosi-Kessel wrote:
> Cygwin used to run very quickly for me; now it doesn't. Not sure when it
> stopped -- last few weeks.
Another data point: I just did a completely fresh (i.e. from scratch)
local drive bare-bones installation (just shell, coreutils, etc) i
On Mon, Oct 1, 2012 at 11:49 AM, Adam Kessel wrote:
> On Sun, Sep 30, 2012 at 4:43 PM, Adam Rosi-Kessel
> wrote:
>> Cygwin used to run very quickly for me; now it doesn't. Not sure when it
>> stopped -- last few weeks.
>
> Another data point: I just did a completely fresh (i.e. from scratch)
> lo
On 10/1/2012 8:22 AM, Adam Kessel wrote:
On Mon, Oct 1, 2012 at 9:33 AM, jojelino wrote:
if the SkyDrive is trademark of M$ and if it needs network connection to remote
server, it would piss you off like you have been experienced.
If it is the case, please stop using *Skydrive* mounted directo
On Mon, Oct 1, 2012 at 12:01 PM, Earnie Boyd
wrote:
> You've not excluded any other changes in your environment. What
> network mapped devices do you have? Are they still available. If not
> the system will wait for the network timeout to occur before moving to
> the next device.
Same slowness
On Mon, Oct 1, 2012 at 12:01 PM, Gregory M. Turner wrote:
> Did you at least try chainging your ${HOME} to somewhere normal and seeing
> what happens? Perhaps SkyDrive has some feature that makes Cygwin crazy.
> For example, your cygwin could have inotify listeners on ${HOME} which could
Yeah, I
On 10/1/2012 12:16 PM, Adam Kessel wrote:
On Mon, Oct 1, 2012 at 12:01 PM, Gregory M. Turner wrote:
Did you at least try chainging your ${HOME} to somewhere normal and seeing
what happens? Perhaps SkyDrive has some feature that makes Cygwin crazy.
For example, your cygwin could have inotify li
On Mon, Oct 1, 2012 at 11:22 AM, Adam Kessel wrote:
>
> On Mon, Oct 1, 2012 at 9:33 AM, jojelino wrote:
> > if the SkyDrive is trademark of M$ and if it needs network connection to
> > remote server, it would piss you off like you have been experienced.
> > If it is the case, please stop using *Sky
On Mon, Oct 1, 2012 at 12:44 PM, Bill Ross wrote:
> Just in case: do you have bash completions turned on? If so, try turning
> them off. Probably a different issue, but it's the other case of bash
> slowness that's come up in the last year or so.
Yes, I uninstalled the completion package entirely
On Mon, Oct 1, 2012 at 12:39 PM, Ken Brown wrote:
>>> Did you at least try chainging your ${HOME} to somewhere normal and
>>> seeing
>>> what happens? Perhaps SkyDrive has some feature that makes Cygwin crazy.
>>> For example, your cygwin could have inotify listeners on ${HOME} which
>>> could
>>
On 10/1/2012 12:55 PM, Adam Kessel wrote:
On Mon, Oct 1, 2012 at 12:39 PM, Ken Brown wrote:
Did you at least try chainging your ${HOME} to somewhere normal and
seeing
what happens? Perhaps SkyDrive has some feature that makes Cygwin crazy.
For example, your cygwin could have inotify listeners
On Mon, Oct 1, 2012 at 1:27 PM, Ken Brown wrote:
> In a standard Cygwin install, the script
> /etc/postinstall/000-cygwin-post-install.sh runs 'mkpasswd -l -c >
> /etc/passwd', which sets the home directory for each user. Normally this is
> /home/username, but you can check it by looking at /etc/
Adam Kessel writes:
> I also tried a brand new install into a new directory with default
> settings, both of 1.7 and legacy 1.5. Still no difference (1.5 is
> actually even slower).
I've had a similar problem about a year ago. The symptom was that each
command from Cygwin would make lsass.exe max
On Mon, Oct 1, 2012 at 1:32 PM, Adam Kessel wrote:
>> specified in /etc/passwd) if it doesn't exist. This assumes that HOME is
>> not set in the Windows environment. Are you seeing something different?
>
> Yes. I just installed from scratch -- download setup.exe and specify a
> new directory for
On 10/1/2012 1:32 PM, Adam Kessel wrote:
On Mon, Oct 1, 2012 at 1:27 PM, Ken Brown wrote:
In a standard Cygwin install, the script
/etc/postinstall/000-cygwin-post-install.sh runs 'mkpasswd -l -c >
/etc/passwd', which sets the home directory for each user. Normally this is
/home/username, but
On 10/1/2012 9:39 AM, Ken Brown wrote:
On 10/1/2012 12:16 PM, Adam Kessel wrote:
On Mon, Oct 1, 2012 at 12:01 PM, Gregory M. Turner wrote:
Did you at least try chainging your ${HOME} to somewhere normal and
seeing
what happens? Perhaps SkyDrive has some feature that makes Cygwin
crazy.
For ex
On Mon, Oct 1, 2012 at 1:50 PM, Ken Brown wrote:
> Two people in this thread have suggested that you check for BLODA, but you
> haven't responded to that. Also, you haven't yet attached cygcheck output
> as requested at
OK, now this is strange -- I thought I had checked BLODA (responded in
separ
On Mon, Oct 1, 2012 at 6:05 PM, Adam Kessel wrote:
> OK, now this is strange -- I thought I had checked BLODA (responded in
> separate thread about ESET), but just now I killed a bunch of things
> in my systray, and suddenly cygwin was fast again. Then I restarted
> all of the tasks I had killed,
On Mon, Oct 1, 2012 at 8:45 PM, Adam Kessel wrote:
> So after a reboot--still fast. This is after a month or so of
> slowness. But I didn't change anything about my configuration!
Now I'm really confused.
cygwin was very slow -- then I killed Dropbox, and it sped back up.
But after a while it re
On Mon, Oct 1, 2012 at 9:59 PM, Adam Kessel wrote:
> Now I'm really confused.
>
> cygwin was very slow -- then I killed Dropbox, and it sped back up.
> But after a while it reverted to slow again (without Dropbox
> restarting). I've repeated this behavior with a few other tasks--same
> thing happe
On 10/01/2012 06:59 PM, Adam Kessel wrote:
On Mon, Oct 1, 2012 at 8:45 PM, Adam Kessel wrote:
So after a reboot--still fast. This is after a month or so of
slowness. But I didn't change anything about my configuration!
Now I'm really confused.
cygwin was very slow -- then I killed Dropbox, an
Greetings, Adam Kessel!
> On Mon, Oct 1, 2012 at 9:59 PM, Adam Kessel wrote:
>> Now I'm really confused.
>>
>> cygwin was very slow -- then I killed Dropbox, and it sped back up.
>> But after a while it reverted to slow again (without Dropbox
>> restarting). I've repeated this behavior with a few
On Tue, Oct 2, 2012 at 6:04 AM, Andrey Repin wrote:
> This suggest that you're looking into wrong direction, and real culprit is
> something you didn't caught yet.
> Try HijackThis http://sourceforge.net/projects/hjt/ to see if there's any
> suspicious handlers installed in your system.
> Or you m
26 matches
Mail list logo
