Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 To: cygwin AT cygwin DOT com From: "Krzysztof Duleba" Subject: Re: remote ipc fails Date: Sat, 15 May 2004 20:46:47 +0200 Lines: 18 Message-ID: References: <20040515162224 DOT GD25768 AT coe DOT bosbc DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: fw-gw-atm.mimuw.edu.pl X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 Christopher Faylor wrote: > On Sat, May 15, 2004 at 05:58:44PM +0200, Krzysztof Duleba wrote: > >I use cygserver to provide IPC queues, shared memory and semafors. > >Everything works ok if running locally. However, if I login remotely, I > >get "Bad system call" even on ipcs. Is it a bug and should I send a > >complete report, or is this behaviour expected? > > Please send a complete report. I ran cygcheck twice - first time from local console, and second via ssh. There were some differences. It came out that in CYGWIN variable, in case of ssh, there was no "server". I reconfigured sshd to use CYGWIN = ntsec tty server and now everything works fine. Regards Krzysztof Duleba -- 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/