[Samba] Samba Transfer Efficiency

[Henri Cook]

Afternoon all,
I'm running a transfer setup as follows:
A - B - C - fairly simple, B initiates a transfer from A to C - B is a 
vital intermediary as it bridges two otherwise seperate networks.
All machines have onboard Gigabit ethernet, A+B are connected via 
Crossover and B-C is connected by very fast switch (i.e. all 
connections should be able to use the full gig if they wanted to)
I see an average of about 23-25% usage in both the crossover (A-B) and 
the connection (B-C) - are there any tricks you can recommend for me to 
speed up my transfers?

Box A is the box running Samba 3.5.1-42.el5
Box B is Win Server 2003
Box C is a NAS (BSD)
I've found a lot of what seems to be outdated information online like 
changing my SNDBUF to 8192 so I thought i'd drop an email to the list 
for more up to date information.

Many thanks,
Henri
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Using the 'WatchSubDirectories' setting in a .NET FileSystemWatcher with a Samba Share

[Henri Cook]

Hi all,

I've just managed to upgrade to Samba 3.3 and am pretty ecstatic about 
finding i can now use FileSystemWatcher to watch for file changes in a 
directory. On a Windows system however, when I say 'watch $dir' with 
watchsubdirectories == true and $dir/a/file.jpg is changed, I get a 
filechanged notification - on Samba 3.3 this doesn't happen - does 
anyone know if it's a bug that was fixed, or something that's not being 
approached?


I do get notifications for files in $dir with the above example. Is 
there anyway I can watch for changes in $dir/a/ $dir/b/ etc with my .NET 
program?


References for these filesystem-level onchange events:

http://lists.samba.org/archive/samba/2006-February/117361.html - Back in 
2006 was when the first support for these events was implemented, i'm 
really wondering whether anyone knows if it's come any further than this 
- or whether it's a bug that's looking to be fixed, or whether it's 
simply never going to make it into Samba?


Thanks in advance, first post to the list - whoop!

Henri
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba