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 Date: Fri, 19 Jul 2002 14:53:34 -0400 (EDT) From: David E Euresti To: Chris January cc: Subject: Re: bash lookups In-Reply-To: <004401c22f51$fa5f4800$0100a8c0@atomice.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm moving this to cygwin. sfsrwcd is my program that's capturing these nfs calls. Don't worry about it. I don't think I'm opening /dev/dsp. Unless ls -la is opening /dev/dsp that I hope it doesn't. The only mention online I can find about these devices is some Queries to the registry. The biggest problem is that I don't know who's causing these lookups. strace seems to think it's not ls. But FileMonitor seems to think it is. So my current theory is that it's related to winmm.dll. Maybe when the dll unloads it tries to close up all these files. But I haven't tested my theory yet. David On Fri, 19 Jul 2002, Chris January wrote: > > So this is very strange. I have some files stored in NFS, for some reason > > when I cd into a directory in NFS and 'ls' it acceses all the files > > nicely. (i.e. one lookup for each file, plus some extra dll's) > > > > However ls -l accesses all these other files: > > sfsrwcd: LOOKUP: winmm.dll > > sfsrwcd: LOOKUP: wave1 > > sfsrwcd: LOOKUP: wave2 > > sfsrwcd: LOOKUP: wave3 > > sfsrwcd: LOOKUP: wave4 > > sfsrwcd: LOOKUP: wave5 > > sfsrwcd: LOOKUP: wave6 > > sfsrwcd: LOOKUP: wave7 > > sfsrwcd: LOOKUP: wave8 > > sfsrwcd: LOOKUP: wave9 > > sfsrwcd: LOOKUP: midi1 > > sfsrwcd: LOOKUP: midi2 > > sfsrwcd: LOOKUP: midi3 > > sfsrwcd: LOOKUP: midi4 > > sfsrwcd: LOOKUP: midi5 > > sfsrwcd: LOOKUP: midi6 > > sfsrwcd: LOOKUP: midi7 > > sfsrwcd: LOOKUP: midi8 > > sfsrwcd: LOOKUP: midi9 > > sfsrwcd: LOOKUP: mmdrv.dll > > sfsrwcd: LOOKUP: aux1 > > sfsrwcd: LOOKUP: aux2 > > sfsrwcd: LOOKUP: aux3 > > sfsrwcd: LOOKUP: aux4 > > sfsrwcd: LOOKUP: aux5 > > sfsrwcd: LOOKUP: aux6 > > sfsrwcd: LOOKUP: aux7 > > sfsrwcd: LOOKUP: aux8 > > sfsrwcd: LOOKUP: aux9 > > sfsrwcd: LOOKUP: mixer1 > > sfsrwcd: LOOKUP: mixer2 > > sfsrwcd: LOOKUP: mixer3 > > sfsrwcd: LOOKUP: mixer4 > > sfsrwcd: LOOKUP: mixer5 > > sfsrwcd: LOOKUP: mixer6 > > sfsrwcd: LOOKUP: mixer7 > > sfsrwcd: LOOKUP: mixer8 > > sfsrwcd: LOOKUP: mixer9 > > > > And in the presence of cygwin symlinks (symlink.lnk) ls -l does the > > following for each symlink > > sfsrwcd: LOOKUP: symlink > > sfsrwcd: LOOKUP: symlink.exe > > sfsrwcd: LOOKUP: symlink.exe > > sfsrwcd: LOOKUP: symlink.exe.lnk > > sfsrwcd: LOOKUP: symlink > > sfsrwcd: LOOKUP: symlink.exe > > sfsrwcd: LOOKUP: symlink.exe > > sfsrwcd: LOOKUP: symlink.exe.lnk > > > > Is there a way to switch off the devices lookup above? > What's sfsrwcd? > Are you opening /dev/dsp? > > Chris > > > -- 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/