search for: findfirst

...D 0 Thu Oct 31 09:15:08 1996 WORKSTATION LEASING .url 75 Thu Jan 23 13:30:10 1997 Todone.doc 16384 Thu Jan 16 16:19:54 1997 assetfld.doc 31744 Tue Jul 29 11:03:20 1997 \work\ FINDFIRST gave ERRSRV - ERRerror (Non-specific error code.) \misc\ received 3 entries (eos=1 resume=0) . D 0 Thu Aug 15 09:30:14 1996 .. D 0 Thu Aug 15 09:30:14 1996 X-Comics.sale 64214 F...

Hi! Here's a patch that allows Linux smbfs to list large directories (i.e. > 100 items) when talking to an OS/2 server. There is a misunderstanding about the flags sent in the FINDFIRST request which causes the OS/2 server to indicate an EOS (end of search) in the FINDFIRST response, even when there are more items to be listed. The result is that smbfs will display only the first ~120 items in a directory (varies with file name length and buffer size) without getting an error mess...

...@aladdin.de > - * - added posix semantics for unlink > - * March 2000, tridge > - * - removed support for old protocol levels. It didn't work anyway > and > - * was cluttering things up a lot. > + * 20/03/00 (chrisp) > + * - fixed FINDFIRST flags for OS/2 Server > + * - added lastname/mask stuff back (OS/2 needs it) And you remove the nice "posix semantics for unlink". It looks like you have simply gone back to the 2.2.14/15 version, and then added findfirst/lastname things. Maybe you could make a smaller patc...

...and options in the smb.conf file, many having to do with performance, but I could use a pointer. When the users try to open a file, the select file listbox in ANY windows app is taking an eternity to populate. The transfer speed of the files is fine, but is there a paticular way to speed up the findfirst/findnext loop that populates the list? Thanks! Mike- -- Mornings: Evolution in action. Only the grumpy will survive. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-att...

...NFS share which are absent on the > block storage share. Samba relies on being able to do offset = telldir() and then seekdir(offset) returning us to the same position in the directory listing. If you think about this you'll see why. Imaginary case, directory with files a-z. Client does findfirst with 1k buffer, server enumerates files one by one, but when it gets to "m" it finds it doesn't have enough room to marshall the client response. No worries, we saved off the 'offset = telldir()' before doing the readdir that returned filename "m". So we seek back t...

...l:GlobalHandle16 019f 08260ca8:Call WPROCS.133: INT_INT21HANDLER() ret=02cf:539f ds=0a17 AX=4e52 BX=0a17 CX=0016 DX=0dfa SI=0114 DI=0e14 ES=0a17 EFL=00000292 08260ca8:trace:int21:DOS3Call AX=4e52 BX=0a17 CX=0016 DX=0dfa SI=0114 DI=0e14 DS=0a17 ES=0a17 EFL=00000292 08260ca8:trace:int21:DOS3Call FINDFIRST mask 0x0016 spec E:\EBT23\BIN\dynatext.ini 08260ca8:trace:dosfs:DOSFS_GetFullName L"E:\\EBT23\\BIN\\dynatext.ini" (last=0) 08260ca8:trace:string:lstrcpynA (0x411c1c84, "/opt/samba-dir", 1024) 08260ca8:trace:dosfs:DOSFS_FindUnixName /opt/samba-dir,L"EBT23\\BIN\\dynatext.ini&...

I'm trying to get to the bottom of where the normal directory functions differ in results for block storage compared to NFS. I created a short c script to look at the offsets generated for the directory when block storage backed in comparison to NFS backed. block storage backed are always positive: File: 5050, Offset: 9213006461214587617 File: 6567, Offset: 9218690536865144001 File: 4033,

...- added posix semantics for unlink > > - * March 2000, tridge > > - * - removed support for old protocol levels. It didn't work anyway > > and > > - * was cluttering things up a lot. > > + * 20/03/00 (chrisp) > > + * - fixed FINDFIRST flags for OS/2 Server > > + * - added lastname/mask stuff back (OS/2 needs it) > > And you remove the nice "posix semantics for unlink". > > It looks like you have simply gone back to the 2.2.14/15 version, and then > added findfirst/lastname things. Maybe y...

...d be interested in the outcome. Seems that Solaris with Samba with large number of files in a single directory is not a good mix! Doing a network trace the, time it takes samba to respond goes up significantly with the more files in that directory. In tests with an application doing basically a findfirst for every file gave the following results: Directory with 3000 files Reply for 'file found': 16ms Reply for 'file not found': 47ms Directory with 9000 files Reply for 'file found': 31 - 62ms Reply for 'file not found': 125ms Directory with ~17000 files Reply for '...

...id a tight loop waiting for revoke to complete. * BUG 12723: ctdb_event monitor command crashes if event is not specified. * BUG 12733: ctdb-docs: Fix documentation of "-n" option to 'ctdb tool'. o Volker Lendecke <vl at samba.org> * BUG 12558: smbd: Fix smb1 findfirst with DFS. * BUG 12610: smbd: Do an early exit on negprot failure. * BUG 12699: winbindd: Fix substitution for 'template homedir'. o Stefan Metzmacher <metze at samba.org> * BUG 12554: s4:kdc: Disable principal based autodetected referral detection. * BUG 12613: idmap_aut...

...id a tight loop waiting for revoke to complete. * BUG 12723: ctdb_event monitor command crashes if event is not specified. * BUG 12733: ctdb-docs: Fix documentation of "-n" option to 'ctdb tool'. o Volker Lendecke <vl at samba.org> * BUG 12558: smbd: Fix smb1 findfirst with DFS. * BUG 12610: smbd: Do an early exit on negprot failure. * BUG 12699: winbindd: Fix substitution for 'template homedir'. o Stefan Metzmacher <metze at samba.org> * BUG 12554: s4:kdc: Disable principal based autodetected referral detection. * BUG 12613: idmap_aut...

...reconnects Total vfs operations: 525 maximum at one time: 3 1) \\chiprodfs2\company SMBs: 305 Oplock Breaks: 0 Reads: 0 Bytes: 0 Writes: 0 Bytes: 0 Flushes: 0 Locks: 0 HardLinks: 0 Symlinks: 0 Opens: 0 Closes: 0 Deletes: 0 Posix Opens: 0 Posix Mkdirs: 0 Mkdirs: 0 Rmdirs: 0 Renames: 0 T2 Renames 0 FindFirst: 2 FNext 0 FClose 0 What is this ???

Hi, I was looking through isolinux and noticed you had trouble detecting 8086 cpu's. I have some experience with this so I thought you might like some different info. The behavior of the "push sp" instruction changed after the 8086 to pushing sp before updating it. I've included a snippet of one of my bootstraps in case you want to use it (or just want to understand better).

...D 0 Thu Jun 5 13:43:08 1997 CaveDog D 0 Thu Jul 10 12:07:56 1997 Ynt3.exe A 594678 Fri Mar 28 08:20:30 1997 outlimep.exe A 491800 Thu Jul 3 11:25:40 1997 \CaveDog\ FINDFIRST gave ERRSRV - ERRerror (Non-specific error code.) 65254 blocks of size 32768. 49863 blocks available Total bytes listed: 1086478 smb: \> -Ernie -- http://www.geocities.com/SiliconValley/Park/9276 _____/ ____ / /Ernie "Shokk" Oporto-SysAdm...

Mounted a smbfs filesystem from windows 2000 server. I am not able to list about 1500 files in the mounted directory, the other directories are OK. The error I've got: smb_proc_readdir_long: name=, result=-2, rcls=1, err=123 Found no solution after searching maillist archives. System - RH7.3, 2.4.18 with xfs acl, samba-2.2.5-1. Thanks for any help. Egidijus Antanaitis

...director"), is there a way I can test for that? To put it differently, I need a kind of proof that the problem is _not_ server side (of which I'm pretty sure, but I need some evidence or hint of some kind). Are there debugging options I need to turn on to trace that? How can I trace, say, FindFirst("*") calls (whatever they are)? I can tcpdump the traffic if needed (I'm actually doing that, but it seems it shows too few details for SMB packets). (please Cc: me since I'm not subscribed) TIA, .TM. -- ____/ ____/ / / / / Marco Colombo ___/ ___...

...of Samba on a Linux 2.4.x machine. I upgraded to 3.0.21b from the Debian package, no change. Strangely enough, tarring up the "bad" directory tree and dropping it on another Samba 3.0.21b server doesn't seem to reproduce the problem. tcpdump seems to indicate that Samba is sending a FINDFIRST response that the client is ignoring, but I may be misreading things. Here are some logs: relevant portion of log.smbd at debug level 10: http://www.eskimo.com/~adam/samba/noogie.log.smbd.trimmed binary libpcap capture of relevant packets, after setting samba to use port 139 so tcpdump recognize...

Says it all really. I'm hoping there's some escape char trick I could do to make this work? Recursing through all the directories would obviously work, but this is for a script that runs over the WAN, so performance is a major issue - I literally just want to see if a file exists in one of the next layers down. Just getting the wildcard through (I think CIFS allows that?) would solve the

...t the full NT format, but one of the calls generates the > SMBgetattrE request which truncates the last bit of the seconds > value, so even though NT is returning the value in 100ns units > the precision is only to the nearest 2 seconds. Of course the NT > call which uses SMBtrans2-findfirst always gets exactly the > right value, so they don't match. Samba provides various configuration options to alleviate timestamp (and granularity) problems (some specifically to solve similar problems with Visual Studio). I've tried experimenting with dos filetimes dos filetime...

Hi, Server is debian lenny w/ samba 3.3.9. Client is mac osx 10.5.x Client tries to copy a folder on share. Only the folder is copied, it's contents are not. An extra step is needed by the client to copy the contents into the new folder on the share. Anyone know of this problem? regards, Ryan