[newlib-cygwin] Add IBM Security Trusteer Rapport to BLODA list
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=debaf9557e7bf4e406985e659f73b11fa405e283 commit debaf9557e7bf4e406985e659f73b11fa405e283 Author: Corinna Vinschen <cori...@vinschen.de> Date: Sun Feb 12 12:15:32 2017 +0100 Add IBM Security Trusteer Rapport to BLODA list Signed-off-by: Corinna Vinschen <cori...@vinschen.de> Diff: --- winsup/doc/faq-using.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index deb7c7e..bb26b83 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1298,6 +1298,7 @@ behaviour which affect the operation of other programs, such as Cygwin. Webroot Spy Sweeper with Antivirus Windows Defender Windows LiveOneCare +IBM Security Trusteer Rapport (see http://www-03.ibm.com/software/products/en/trusteer-rapport;>its home page Sometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable
[newlib-cygwin] faq: Sort BLODA list and update advice on fixing fork failures
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=930474058e4596b652c4b42d9e6eea6c294db9c1 commit 930474058e4596b652c4b42d9e6eea6c294db9c1 Author: Jon Turney <jon.tur...@dronecode.org.uk> Date: Mon Mar 7 18:42:41 2016 + faq: Sort BLODA list and update advice on fixing fork failures * faq-using.xml (bloda): Alphabetically sort BLODA list for ease of finding things in it. (fixing-fork-failures): Update to suggest rebase-trigger rather than running rebaseall via dash yourself. Mention detect_bloda CYGWIN token. Signed-off-by: Jon Turney <jon.tur...@dronecode.org.uk> Diff: --- winsup/doc/faq-using.xml | 88 ++-- 1 file changed, 56 insertions(+), 32 deletions(-) diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index f6d4b8e..66e133b 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1286,39 +1286,39 @@ behaviour which affect the operation of other programs, such as Cygwin. Among the software that has been found to cause difficulties are: -Sonic Solutions burning software containing DLA component (when DLA disabled) -Norton/McAfee/Symantec antivirus or antispyware -Logitech webcam software with "Logitech process monitor" service -Kerio, Agnitum or ZoneAlarm Personal Firewall -Iolo System Mechanic/AntiVirus/Firewall -LanDesk -Windows Defender -Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center -NOD32 Antivirus -ByteMobile laptop optimization client -Earthlink Total-Access -Spybot SD TeaTimer AR Soft RAM Disk ATI Catalyst (some versions) -NVIDIA GeForce (some versions) -Windows LiveOneCare -Webroot Spy Sweeper with Antivirus -COMODO Firewall Pro -PC Tools Spyware Doctor +AVAST (disable FILESYSTEM and BEHAVIOR realtime shields) Avira AntiVir -Panda Internet Security BitDefender -Google Desktop -Sophos Anti-Virus 7 Bufferzone from Trustware -Lenovo IPS Core Service (ipssvc) -Lenovo RapidBoot Shield -Credant Guardian Shield -AVAST (disable FILESYSTEM and BEHAVIOR realtime shields) +ByteMobile laptop optimization client +COMODO Firewall Pro Citrix Metaframe Presentation Server/XenApp (see http://support.citrix.com/article/CTX107825;>Citrix Support page) -Lavasoft Web Companion +Credant Guardian Shield +Earthlink Total-Access Forefront TMG +Google Desktop +Iolo System Mechanic/AntiVirus/Firewall +Kerio, Agnitum or ZoneAlarm Personal Firewall +LanDesk +Lavasoft Web Companion +Lenovo IPS Core Service (ipssvc) +Lenovo RapidBoot Shield +Logitech webcam software with "Logitech process monitor" service MacType +NOD32 Antivirus +NVIDIA GeForce (some versions) +Norton/McAfee/Symantec antivirus or antispyware +PC Tools Spyware Doctor +Panda Internet Security +Sonic Solutions burning software containing DLA component (when DLA disabled) +Sophos Anti-Virus 7 +Spybot SD TeaTimer +Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center +Webroot Spy Sweeper with Antivirus +Windows Defender +Windows LiveOneCare Sometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable @@ -1398,16 +1398,40 @@ such as virtual memory paging and file caching. Ensure that you have eliminated (not just disabled) all software on the . -Read the 'rebase' package README in -/usr/share/doc/rebase/, and follow the -instructions there to run 'rebaseall'. Switch from 32-bit Cygwin to 64-bit Cygwin, if your OS and CPU support that. With the bigger address space fork() is less likely to fail. + + + Try setting the environment variable CYGWIN to "detect_bloda", which + enables some extra debugging, which may indicate what other software is + causing the problem. + + + See https://cygwin.com/ml/cygwin/2012-02/msg00797.html;>this + mail for more information. + + + + + Force a full rebase: Run rebase-trigger fullrebase, + exit all Cygwin programs and run Cygwin setup. + + + By default, Cygwin's setup program automatically performs an incremental + rebase of newly installed files. Forcing a full rebase causes the + rebase map to be cleared before doing the rebase. + + + See /usr/share/doc/rebase/README and + /usr/share/doc/Cygwin/_autorebase.README for more + details. + + Please note that installing new packages or updating existing + ones undoes the effects of rebase and often causes fork() failures to + reappear. + + - Please note that installing new packages or updating existing - ones undoes the effects of rebaseall and often causes fork() failures - to reappear. If so, just run rebaseall again.
Re: [PATCH] faq: Sort BLODA list and update advice on fixing fork failures
Hi Jon, On Mar 8 11:14, Jon Turney wrote: > * faq-using.xml(bloda): Alphabetically sort BLODA list for ease of > finding things in it. (fixing-fork-failures) Update to suggest > rebase-trigger rather than running rebaseall via dash yourself. > Mention detect_bloda CYGWIN token. Can you clean up formatting of this log entry before applying? In theory the patch itself is ok. I'm just wondering for a while now if the detect_bloda option should be removed. I don't remember any useful BLODA report as a result of using it. But my memory could be wrong here, do you have a different experience? If so, feel free to check in your patch as is. Thanks. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
[PATCH] faq: Sort BLODA list and update advice on fixing fork failures
* faq-using.xml(bloda): Alphabetically sort BLODA list for ease of finding things in it. (fixing-fork-failures) Update to suggest rebase-trigger rather than running rebaseall via dash yourself. Mention detect_bloda CYGWIN token. Signed-off-by: Jon Turney <jon.tur...@dronecode.org.uk> --- winsup/doc/faq-using.xml | 88 ++-- 1 file changed, 56 insertions(+), 32 deletions(-) diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index ae72145..9194677 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1286,39 +1286,39 @@ behaviour which affect the operation of other programs, such as Cygwin. Among the software that has been found to cause difficulties are: -Sonic Solutions burning software containing DLA component (when DLA disabled) -Norton/McAfee/Symantec antivirus or antispyware -Logitech webcam software with "Logitech process monitor" service -Kerio, Agnitum or ZoneAlarm Personal Firewall -Iolo System Mechanic/AntiVirus/Firewall -LanDesk -Windows Defender -Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center -NOD32 Antivirus -ByteMobile laptop optimization client -Earthlink Total-Access -Spybot SD TeaTimer AR Soft RAM Disk ATI Catalyst (some versions) -NVIDIA GeForce (some versions) -Windows LiveOneCare -Webroot Spy Sweeper with Antivirus -COMODO Firewall Pro -PC Tools Spyware Doctor +AVAST (disable FILESYSTEM and BEHAVIOR realtime shields) Avira AntiVir -Panda Internet Security BitDefender -Google Desktop -Sophos Anti-Virus 7 Bufferzone from Trustware -Lenovo IPS Core Service (ipssvc) -Lenovo RapidBoot Shield -Credant Guardian Shield -AVAST (disable FILESYSTEM and BEHAVIOR realtime shields) +ByteMobile laptop optimization client +COMODO Firewall Pro Citrix Metaframe Presentation Server/XenApp (see http://support.citrix.com/article/CTX107825;>Citrix Support page) -Lavasoft Web Companion +Credant Guardian Shield +Earthlink Total-Access Forefront TMG +Google Desktop +Iolo System Mechanic/AntiVirus/Firewall +Kerio, Agnitum or ZoneAlarm Personal Firewall +LanDesk +Lavasoft Web Companion +Lenovo IPS Core Service (ipssvc) +Lenovo RapidBoot Shield +Logitech webcam software with "Logitech process monitor" service MacType +NOD32 Antivirus +NVIDIA GeForce (some versions) +Norton/McAfee/Symantec antivirus or antispyware +PC Tools Spyware Doctor +Panda Internet Security +Sonic Solutions burning software containing DLA component (when DLA disabled) +Sophos Anti-Virus 7 +Spybot SD TeaTimer +Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center +Webroot Spy Sweeper with Antivirus +Windows Defender +Windows LiveOneCare Sometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable @@ -1398,14 +1398,38 @@ such as virtual memory paging and file caching. Ensure that you have eliminated (not just disabled) all software on the . -Read the 'rebase' package README in -/usr/share/doc/rebase/, and follow the -instructions there to run 'rebaseall'. + + + Try setting the environment variable CYGWIN to "detect_bloda", which + enables some extra debugging, which may indicate what other software is + causing the problem. + + + See https://cygwin.com/ml/cygwin/2012-02/msg00797.html;>this + mail for more information. + + + + + Force a full rebase: Run rebase-trigger fullrebase, + exit all Cygwin programs and run Cygwin setup. + + + By default, Cygwin's setup program automatically performs an incremental + rebase of newly installed files. Forcing a full rebase causes the + rebase map to be cleared before doing the rebase. + + + See /usr/share/doc/rebase/README and + /usr/share/doc/Cygwin/_autorebase.README for more + details. + + Please note that installing new packages or updating existing + ones undoes the effects of rebase and often causes fork() failures to + reappear. + + - Please note that installing new packages or updating existing - ones undoes the effects of rebaseall and often causes fork() failures - to reappear. If so, just run rebaseall again. - See the https://cygwin.com/cygwin-ug-net/highlights.html#ov-hi-process;> process creation section of the User's Guide for the technical reasons it is so difficult to make fork() work reliably. -- 2.7.0
[newlib-cygwin] Add Lavasoft Web Companion to BLODA list.
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=901af8695eba12a32384adfe128037c65c78576e commit 901af8695eba12a32384adfe128037c65c78576e Author: Jon TURNEY jon.tur...@dronecode.org.uk Date: Tue Aug 18 17:24:10 2015 +0100 Add Lavasoft Web Companion to BLODA list. 2015-08-18 Jon Turney jon.tur...@dronecode.org.uk * faq-using.xml (faq.using.bloda): Add Lavasoft Web Companion to BLODA list. Signed-off-by: Jon TURNEY jon.tur...@dronecode.org.uk Diff: --- winsup/doc/ChangeLog | 5 + winsup/doc/faq-using.xml | 1 + 2 files changed, 6 insertions(+) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 9cff0e4..02061ff 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2015-08-18 Jon Turney jon.tur...@dronecode.org.uk + + * faq-using.xml (faq.using.bloda): Add Lavasoft Web Companion to + BLODA list. + 2015-08-03 Jon Turney jon.tur...@dronecode.org.uk * faq-programming.xml: Improve debugging-cygwin answer. diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index 372888f..87ec112 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1274,6 +1274,7 @@ behaviour which affect the operation of other programs, such as Cygwin. listitemparaCredant Guardian Shield/para/listitem listitemparaAVAST (disable FILESYSTEM and BEHAVIOR realtime shields)/para/listitem listitemparaCitrix Metaframe Presentation Server/XenApp (see ulink url=http://support.citrix.com/article/CTX107825;Citrix Support page/ulink)/para/listitem +listitemparaLavasoft Web Companion/para/listitem /itemizedlist/para paraSometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable
Re: [PATCH] Add Lavasoft Web Companion to BLODA list.
On Aug 18 17:25, Jon TURNEY wrote: 2015-08-18 Jon Turney jon.tur...@dronecode.org.uk * faq-using.xml (faq.using.bloda): Add Lavasoft Web Companion to BLODA list. Signed-off-by: Jon TURNEY jon.tur...@dronecode.org.uk --- winsup/doc/ChangeLog | 5 + winsup/doc/faq-using.xml | 1 + 2 files changed, 6 insertions(+) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 9cff0e4..02061ff 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2015-08-18 Jon Turney jon.tur...@dronecode.org.uk + + * faq-using.xml (faq.using.bloda): Add Lavasoft Web Companion to + BLODA list. + 2015-08-03 Jon Turney jon.tur...@dronecode.org.uk * faq-programming.xml: Improve debugging-cygwin answer. diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index 372888f..87ec112 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1274,6 +1274,7 @@ behaviour which affect the operation of other programs, such as Cygwin. listitemparaCredant Guardian Shield/para/listitem listitemparaAVAST (disable FILESYSTEM and BEHAVIOR realtime shields)/para/listitem listitemparaCitrix Metaframe Presentation Server/XenApp (see ulink url=http://support.citrix.com/article/CTX107825;Citrix Support page/ulink)/para/listitem +listitemparaLavasoft Web Companion/para/listitem /itemizedlist/para paraSometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable -- 2.4.5 ACK Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpA6yQZeudfn.pgp Description: PGP signature
[PATCH] Add Lavasoft Web Companion to BLODA list.
2015-08-18 Jon Turney jon.tur...@dronecode.org.uk * faq-using.xml (faq.using.bloda): Add Lavasoft Web Companion to BLODA list. Signed-off-by: Jon TURNEY jon.tur...@dronecode.org.uk --- winsup/doc/ChangeLog | 5 + winsup/doc/faq-using.xml | 1 + 2 files changed, 6 insertions(+) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 9cff0e4..02061ff 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2015-08-18 Jon Turney jon.tur...@dronecode.org.uk + + * faq-using.xml (faq.using.bloda): Add Lavasoft Web Companion to + BLODA list. + 2015-08-03 Jon Turney jon.tur...@dronecode.org.uk * faq-programming.xml: Improve debugging-cygwin answer. diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index 372888f..87ec112 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1274,6 +1274,7 @@ behaviour which affect the operation of other programs, such as Cygwin. listitemparaCredant Guardian Shield/para/listitem listitemparaAVAST (disable FILESYSTEM and BEHAVIOR realtime shields)/para/listitem listitemparaCitrix Metaframe Presentation Server/XenApp (see ulink url=http://support.citrix.com/article/CTX107825;Citrix Support page/ulink)/para/listitem +listitemparaLavasoft Web Companion/para/listitem /itemizedlist/para paraSometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable -- 2.4.5
Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
On 02/14/2011 10:13 PM, L Anderson wrote: Thanks for the hint--it allowed me to by-pass the test. However, for the record, based on 'coreutils-8.10-1--configure[3295,3296]', I think you meant: $ cat /usr/share/config.site\EOF # configure gets the right answer, but only after hammering the system gl_cv_func_getcwd_path_max=yes EOF Yes, autoconf looks for share/config.site relative to the --prefix argument, so /usr/share/config.site is the right place for a config.site that affects cygport builds. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
Eric Blake wrote: On 02/06/2011 09:40 PM, L Anderson wrote: In regards to the aforementioned while loop in 'conftest.c'--the logic of it being run for every invocation of a 'coreutils' build escapes me. I can see running it once per OS, outside of the build process, to determine if the given OS does the right thing; after that, shouldn't it just be a case of checking if the OS being used has been tested and deemed to behave properly? Yes, this particular configure test takes a long time, even without virus scanning, on WinXP (where Microsoft has an O(n^2) implementation); it's faster on newer Windows (where Microsoft fixed things to be O(n)). You can pre-seed a config.site cache to skip the test by using a known outcome result (in fact, I do just that when building coreutils): $ cat /usr/config.site\EOF # configure gets the right answer, but only after hammering the system gl_cv_func_getcwd_path_max=yes EOF Thanks for the hint--it allowed me to by-pass the test. However, for the record, based on 'coreutils-8.10-1--configure[3295,3296]', I think you meant: $ cat /usr/share/config.site\EOF # configure gets the right answer, but only after hammering the system gl_cv_func_getcwd_path_max=yes EOF xor $ cat /usr/etc/config.site\EOF # configure gets the right answer, but only after hammering the system gl_cv_func_getcwd_path_max=yes EOF Correct? I used the latter and it did the trick. Regards, LA -- 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
Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
L Anderson wrote: This may be just a case of pilot error that I can't see because, surely, others must have encountered this situation before. I can't say for sure, but recently I had big suspicions about AVG and directories. I have an MFC testsuite for some software unrelated to Cygwin. It creates a temporary directory, creates some files in it, then delete it recursively. This had always worked perfectly on all machines. But recently, some time after installing AVG, the deletion of the temp dir failed with a sharing violation. Strangely, trying to delete that directory 2 times in a row almost fixed the problem. I should try to uninstall AVG to see if this problem goes away. -- Vincent Rivière -- 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
Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
On 02/06/2011 09:40 PM, L Anderson wrote: In regards to the aforementioned while loop in 'conftest.c'--the logic of it being run for every invocation of a 'coreutils' build escapes me. I can see running it once per OS, outside of the build process, to determine if the given OS does the right thing; after that, shouldn't it just be a case of checking if the OS being used has been tested and deemed to behave properly? Yes, this particular configure test takes a long time, even without virus scanning, on WinXP (where Microsoft has an O(n^2) implementation); it's faster on newer Windows (where Microsoft fixed things to be O(n)). You can pre-seed a config.site cache to skip the test by using a known outcome result (in fact, I do just that when building coreutils): $ cat /usr/config.site \EOF # configure gets the right answer, but only after hammering the system gl_cv_func_getcwd_path_max=yes EOF I suppose I should also tweak my coreutils*.cygport file to pre-seed the cache at configure time (by adding gl_cv_func_getcwd_path_max=yes to CYGCONF_ARGS), but that won't help you when upgrading to coreutils-8.10-1.cygport, which came out between your report against 8.8 and this email. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
Vincent Rivière wrote: L Anderson wrote: This may be just a case of pilot error that I can't see because, surely, others must have encountered this situation before. I can't say for sure, but recently I had big suspicions about AVG and directories. I have an MFC testsuite for some software unrelated to Cygwin. It creates a temporary directory, creates some files in it, then delete it recursively. This had always worked perfectly on all machines. But recently, some time after installing AVG, the deletion of the temp dir failed with a sharing violation. Strangely, trying to delete that directory 2 times in a row almost fixed the problem. In all my testing, I have never encountered any thing like a share violation. However, to reconfirm AVG greatly extends the time required to recursively traverse a directory tree, look at the following results of my test. I create then delete a chain of 150 sub-directories recursively. The times given are for 10 consecutive operations. The first set is with AVG enabled, the second with it disabled. As you can see, the enabled times are nonlinear, while the disabled ones are, for the most part, linear (153 seconds vs 22 seconds!). I only show 150 levels because any thing much larger is unbearable. Regards, LA -Test with AVG enabled--- $ testCygport.sh -d O:\ScsiU2WAVGEnabled -t both -m 150 $testFlag: $createFlag: create $deleteFlag: delete $basePath: /cygdrive/o/ScsiU2WAVGEnabled $modVal: 10 $maxDepth: 150 (mkdir/cd) confdir3(0):0 sec.--decending (mkdir/cd) confdir3(10):1 sec.--decending (mkdir/cd) confdir3(20):1 sec.--decending (mkdir/cd) confdir3(30):1 sec.--decending (mkdir/cd) confdir3(40):2 sec.--decending (mkdir/cd) confdir3(50):2 sec.--decending (mkdir/cd) confdir3(60):2 sec.--decending (mkdir/cd) confdir3(70):3 sec.--decending (mkdir/cd) confdir3(80):3 sec.--decending (mkdir/cd) confdir3(90):5 sec.--decending (mkdir/cd) confdir3(100):6 sec.--decending (mkdir/cd) confdir3(110):8 sec.--decending (mkdir/cd) confdir3(120):9 sec.--decending (mkdir/cd) confdir3(130):12 sec.--decending (mkdir/cd) confdir3(140):14 sec.--decending Made or traversed 150 sub-directories in 69 seconds. ***Starting the accent, removing sub-directories*** (cd/rmdir) confdir3(140):31 sec.--accending (cd/rmdir) confdir3(130):14 sec.--accending (cd/rmdir) confdir3(120):11 sec.--accending (cd/rmdir) confdir3(110):9 sec.--accending (cd/rmdir) confdir3(100):7 sec.--accending (cd/rmdir) confdir3(90):6 sec.--accending (cd/rmdir) confdir3(80):5 sec.--accending (cd/rmdir) confdir3(70):4 sec.--accending (cd/rmdir) confdir3(60):3 sec.--accending (cd/rmdir) confdir3(50):2 sec.--accending (cd/rmdir) confdir3(40):2 sec.--accending (cd/rmdir) confdir3(30):1 sec.--accending (cd/rmdir) confdir3(20):2 sec.--accending (cd/rmdir) confdir3(10):1 sec.--accending (cd/rmdir) confdir3(0):1 sec.--accending Back at depth level 0; deleted 150 sub-directories. Decent 69 seconds; accent 84 seconds; total 153 seconds. -Test with AVG disabled- $ testCygport.sh -d O:\ScsiU2WAVGDisabled -t both -m 150 $testFlag: $createFlag: create $deleteFlag: delete $basePath: /cygdrive/o/ScsiU2WAVGDisabled $modVal: 10 $maxDepth: 150 (mkdir/cd) confdir3(0):0 sec.--decending (mkdir/cd) confdir3(10):1 sec.--decending (mkdir/cd) confdir3(20):0 sec.--decending (mkdir/cd) confdir3(30):1 sec.--decending (mkdir/cd) confdir3(40):0 sec.--decending (mkdir/cd) confdir3(50):1 sec.--decending (mkdir/cd) confdir3(60):1 sec.--decending (mkdir/cd) confdir3(70):1 sec.--decending (mkdir/cd) confdir3(80):0 sec.--decending (mkdir/cd) confdir3(90):1 sec.--decending (mkdir/cd) confdir3(100):1 sec.--decending (mkdir/cd) confdir3(110):1 sec.--decending (mkdir/cd) confdir3(120):0 sec.--decending (mkdir/cd) confdir3(130):1 sec.--decending (mkdir/cd) confdir3(140):0 sec.--decending Made or traversed 150 sub-directories in 9 seconds. ***Starting the accent, removing sub-directories*** (cd/rmdir) confdir3(140):2 sec.--accending (cd/rmdir) confdir3(130):1 sec.--accending (cd/rmdir) confdir3(120):1 sec.--accending (cd/rmdir) confdir3(110):1 sec.--accending (cd/rmdir) confdir3(100):0 sec.--accending (cd/rmdir) confdir3(90):1 sec.--accending (cd/rmdir) confdir3(80):1 sec.--accending (cd/rmdir) confdir3(70):1 sec.--accending (cd/rmdir) confdir3(60):1 sec.--accending (cd/rmdir) confdir3(50):1 sec.--accending (cd/rmdir) confdir3(40):1 sec.--accending (cd/rmdir) confdir3(30):1 sec.--accending (cd/rmdir) confdir3(20):1 sec.--accending (cd/rmdir) confdir3(10):0 sec.--accending (cd/rmdir) confdir3(0):1 sec.--accending Back at depth level 0; deleted 150 sub-directories. Decent 9 seconds; accent 13 seconds; total 22 seconds. -- 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
Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
While trying to diagnose another problem, I decided to build the
'coreutils' package so I could check a few things out. I followed the
'coreutils' build instructions...'cygport coreutils-8.8-1 all' and
things went swimmingly up to the point where the messages displayed read:
...
checking whether getnameinfo is declared... (cached) yes
checking for struct addrinfo... yes
checking whether getcwd handles long file names properly...
After waiting a good bit, it appeared progress had stop. Not wanting to
interrupt the build, I left to do other things. Long story short, on my
return, more than 6 hours later, there was no visible signs of
progress--no new messages displayed.
Digging a bit deeper, I found the build process was still running and in
the following chunk of code in 'conftest.c'--doing 'mkdir'--so I killed
the sucker.
code
while (1)
{
size_t dotdot_max = PATH_MAX * (DIR_NAME_SIZE / DOTDOTSLASH_LEN);
char *c = NULL;
cwd_len += DIR_NAME_SIZE;
/* If mkdir or chdir fails, it could be that this system cannot
create
any file with an absolute name longer than PATH_MAX, such as
cygwin.
If so, leave fail as 0, because the current working directory
can't
be too long for getcwd if it can't even be created. For other
errors, be pessimistic and consider that as a failure, too. */
if (mkdir (DIR_NAME, S_IRWXU) 0 || chdir (DIR_NAME) 0)
{
if (! (errno == ERANGE || is_ENAMETOOLONG (errno)))
fail = 20;
break;
}
if (PATH_MAX = cwd_len cwd_len PATH_MAX + DIR_NAME_SIZE)
{
c = getcwd (buf, PATH_MAX);
if (!c errno == ENOENT)
{
fail = 11;
break;
}
if (c || ! (errno == ERANGE || is_ENAMETOOLONG (errno)))
{
fail = 21;
break;
}
}
if (dotdot_max = cwd_len - initial_cwd_len)
{
if (dotdot_max + DIR_NAME_SIZE cwd_len - initial_cwd_len)
break;
c = getcwd (buf, cwd_len + 1);
if (!c)
{
if (! (errno == ERANGE || errno == ENOENT
|| is_ENAMETOOLONG (errno)))
{
fail = 22;
break;
}
if (AT_FDCWD || errno == ERANGE || errno == ENOENT)
{
fail = 12;
break;
}
}
}
if (c strlen (c) != cwd_len)
{
fail = 23;
break;
}
++n_chdirs;
}
/code
Further investigation showed the code really had been running and had
created a chain of more than 1300 'confdir3' sub-directories under the
sub-directory 'build'. I then ran 'cygport coreutils-8.8-1 finish' which
took at least 12 hours more to clean up the mess. (It would have taken
somewhat less time had I known to disable AVG.)
Since I couldn't control the build process, I wrote a test script to
emulate the 'confdir3' sub-directory chain's creation and deletion
behavior to better understand what was going on. My conclusion is that
the above code is a bit nasty. I've further found that the code is
even more nefarious when run with 'AVG Internet Security 2011' enabled.
The running time of my emulation script, with 'AVG' disabled, is long
but almost linear; with 'AVG' enabled, it's much much longer and closer
to polynomial time of order around 10--at least in the range of 0-1000
sub-directories (a1x + a2x^2 + a3x^3 + a4x^4 + a5x^5 + a6x^6 + a10x^10,
with the appropriate selected ais, x=subdir level).
I then run 'cygport coreutils-8.8-1 prep' to verify my findings. I
killed it after a few hours and 1336 'confdir3' subdirs later. I'm
finishing off now with 'cygport coreutils-8.8-1 finish' to clean things
up. It's been at it for a few hours now--quite a few yet to go, I
suspect. Yes! I'm satisfied; it's definitely a nasty bit of code. (I
think it should be removed or fixed to behave better.)
Therefore, for those with 'AVG Internet Security 2011', my advice is to
disable AVG before doing a coreutils build (or any other using
cygport?). You may still have to wait a long time, but not nearly as
long as if it's enabled! I suspect similar behavior will be had with
other anti-viri programs--YMMV.
In regards to the aforementioned while loop in 'conftest.c'--the logic
of it being run for every invocation of a 'coreutils' build escapes me.
I can see running it once per OS, outside of the build process, to
determine if the given OS does the right thing; after that, shouldn't it
just be a case of checking if the OS being used has been tested and
deemed to behave properly?
This may be just a case of pilot error that I can't see because, surely,
others must have encountered this situation before. Perhaps someone
would be
Re: Please add 'AVG Internet Security 2011' to the BLODA list (and cygport also :-) ).
My experience with AVG was very good, as long as I disabled all of its continuous protection features. I mean, I just used it as a scanner. Cygwin worked fine for me in this arrangement. I switched to Microsoft's free MSE because it is good enough for my purposes. But I did not find AVG to be bad. -- 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
Re: BLODA list
Greg Chicares wrote: On 2009-02-21 12:23Z, Vincent R. wrote: Is there any BLODA list ? Yes, it's in the FAQ: It's also built into cygcheck -s. Look for app conflicts. -- 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/
BLODA list
Hi, Is there any BLODA list ? If not I would like to start one and report that the following software is not compatible : Manufacturer : Logitech Process : LVComSrv.exe,LVPrcSvr.exe When I try to compile, everything starts to be very slow and sometimes sh crashs but as soon as I kill LVPrcSvr.exe, things are getting normal. My system : Windows XP SP3, Core2Duo E8200 -- 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/
Re: BLODA list
On Sat, 21 Feb 2009 13:23:57 +0100, Vincent R. foru...@smartmobili.com wrote: Hi, Is there any BLODA list ? If not I would like to start one and report that the following software is not compatible : Manufacturer : Logitech Process : LVComSrv.exe,LVPrcSvr.exe When I try to compile, everything starts to be very slow and sometimes sh crashs but as soon as I kill LVPrcSvr.exe, things are getting normal. My system : Windows XP SP3, Core2Duo E8200 -- 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/ Forget to say that these COM services are used with Logitech QuickCam Pro 5000. I am using the latest version. -- 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/
Re: BLODA list
On 2009-02-21 12:23Z, Vincent R. wrote: Is there any BLODA list ? Yes, it's in the FAQ: http://cygwin.com/faq/faq.using.html#faq.using.bloda and it includes this reference: Logitech webcam software with Logitech process monitor service to the dodgy app you mentioned. -- 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/
