X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-Id: <6.2.5.6.2.20120826114906.05a22e20@binnacle.cx> Date: Sun, 26 Aug 2012 12:00:50 -0400 To: cygwin AT cygwin DOT com From: starlight DOT 2012q3 AT binnacle DOT cx Subject: Re: question: 'nxclient' won't connect with cygwin1.dll 1.7.16 In-Reply-To: <6.2.5.6.2.20120825232351.05a21ae8@flumedata.com> References: <6 DOT 2 DOT 5 DOT 6 DOT 2 DOT 20120825232351 DOT 05a21ae8 AT flumedata DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Received-SPF: pass (mx.binnacle.cx: 172.29.87.10 is whitelisted by SPF-milter whitelist entry) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Narrowed this down some. Posting for future Googlers. Looks like the culprit is probably What's new and what changed from 1.7.7 to 1.7.8 * Drop support for Windows NT4 prior to Service Pack 4. per http://cygwin.com/cygwin-ug-net/ov-new1.7.html Looking at the NXWin log output I get the feeling it's depending on some old filename semantics. First bit of strangeness is that the output of NXWin should go to 'winlog', but in the post 1.7.7 secnario its written to 'svclog', which is intended for the parent of NXWin. The place where NXWin breaks down is Dispatch: Exiting from the dispatcher with exception [2]. also this seems particularly not good Error: Cannot rename 'C:\Users\username\NX73F8~1/D-W2K8NXCLIENT-85AF85472A34ED995AD4DFCD5F3BEFBD' to 'C:\Users\username\NX73F8~1/T-D-W2K8NXCLIENT-85AF85472A34ED995AD4DFCD5F3BEFBD'. Error is 'Permission denied' In case it's relevent, have 'fstab' setup like so none /cygdrive cygdrive binary,posix=0,user,noacl,auto 0 0 It's a guess, but I'd say that NXWin might require work to eliminate some obsolete file semantics. On the other hand the issues could all reside in the X server code and simply recompiling and relinking NXWin in the latest X11 tree will make it right. Till then the 1.7.7 DLL does the job. -- 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