Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3D63BA57.6D248A72@kraglund.net>
Date: Wed, 21 Aug 2002 18:05:43 +0200
From: Flemming Kraglund <fk AT kraglund DOT net>
X-Accept-Language: en
MIME-Version: 1.0
To: Kaj Mikkelsen <kmi AT vitesse DOT com>
CC: cygwin AT cygwin DOT com, fk AT superusers DOT dk,
   Dan Christian Raun Jensen <drj AT vitesse DOT com>
Subject: Re: ls hanging with named pipes through samba
References: <4635C7499BD3A14C9361477F0613ED9B049DFC AT mx-dk1 DOT vsc DOT vitesse DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang)

Hi Kaj

It could be a problem with mapping a named pipe through CIFS through cygwin to ls,
either samba or cygwin could be trying to get some information on a non supported
type (not supported by one of the intervening steps/protocols).

You could try to make samba generate some debug to see which operation the client
(cygwin library) is doing, it could be some other operation that are mapped to an
open (by samba) followed by something or it could be that the client really are
opening the file.

Knowing the CIFS operation samba is responding to will make it possible to see
what and why samba are/is locking and why this blocks other samba daemons.

kill -USR1 <PID> to increase the debug level, newer samba versions has the
smbcontrol (smbcontrol <PID> debug <num>)

/FK

Kaj Mikkelsen wrote:
> 
>    Part 1.1    Type: Plain Text (text/plain)
>            Encoding: quoted-printable

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/