From 930474058e4596b652c4b42d9e6eea6c294db9c1 Mon Sep 17 00:00:00 2001 From: Jon Turney Date: Mon, 7 Mar 2016 18:42:41 +0000 Subject: [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 --- 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 f6d4b8e6a..66e133bfa 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 S&D 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 +ByteMobile laptop optimization client +COMODO Firewall Pro +Citrix Metaframe Presentation Server/XenApp (see Citrix Support page) +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 -Credant Guardian Shield -AVAST (disable FILESYSTEM and BEHAVIOR realtime shields) -Citrix Metaframe Presentation Server/XenApp (see Citrix Support page) -Lavasoft Web Companion -Forefront TMG +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 S&D 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 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 process creation section of the User's Guide for the technical reasons it is so difficult to make fork() work reliably.