On Fri, Oct 15, 2004 at 01:21:28PM +0200, Peter Piechutzki wrote: > Hello, > > thx for the quick response. > > You are certainly right about the oplocks and we had both levels > turned off for testing with the same results. > > After extensive testing and analyzing the sourcecode of openfile() we > are sure that even updating to the newest version of samba wouldn't > solve our problem. > > It is fairly easy to reproduce. > put a foxpro .dbf file on a share from samba into a directory named > '/abc/pipe' Try to import the file into a MS-Access Database and you > will recieve a error 'The microsoft jet ... can't open ... .inf' > > This will also happen if the full directory path is shorter then 9 > characters and ends with 'pipe' for example 'dat_pipe' 'abcdpipe' > 'de/pipe' and so on. > > As i mentioned in my first post samba returns different errer codes to > the smb client machine depending on the directory name.
Yeah, I added that code. I'm now trying to remember what client named pipe open I was trying to prevent here :-(..... I'm wondering what effect just removing this code would have. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
