Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <402FF19D.5070301@cwilson.fastmail.fm> Date: Sun, 15 Feb 2004 17:24:29 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Solved: Still trouble with IPC References: <002d01c3f3e3$328a8350$6402a8c0@humphrey> In-Reply-To: <002d01c3f3e3$328a8350$6402a8c0@humphrey> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Frank Wübbeling wrote: > Looking at the cygwin sources, I realized that any access to cygserver is > disabled unless I explicitly export CYGWIN="server=1". Doing this > immediately solved my problems. Weird. Since cygserver is now the default > IPC code, shouldn't the default for allow_server be "yes"? Not until all of the software that is part of the distribution which currently uses cygipc has been officially switched over to using cygserver. At present, this includes postgresql cygwin-xfree (all packages) xemacs GraphicsMagick ImageMagick gd ddd gv xaw3d openbox fvwm x2x lesstif xwinclip I'm not sure how many of these directly use cygipc themselves, or just need it because they're X programs, and XFree86 needs it. -- Chuck -- 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/