A couple of oddities: 1) (This may be perfectly normal) It seems that when I am writing a largish number of files (say, 200-300 mp3s, a similar number of largish pdfs or zips, etc) to a Samba share, the copy process "staggers". By this I mean that it seems to copy quickly, then stops for a while, goes quickly again, stops for a while, etc. It seems that I can see substantially increased hard drive activity on the Linux box during the apparent stopped time. The Windows XP networking graph makes a sort of jagged sinusoidal pattern of transfer and non-transfer times. During this process, the complete resources of the Linux bix appear to be consumed. For example, if I am watching a video streaming from the Linux box and I copy over the aforementioned boatload of files, the video performance will suffer, if not be entirely shut down. Is this to be expected?
2) If I create a new share, should it be necessary to stop and restart Samba services in order to write to it on the network? It appears to be, for some odd reason. Tangentially, what are all of the conditions which must be met in order for a share to be writable by a Windows machine? I know that last one might be a tall order...
Again, many thanks for all of the help. Samba is running amazingly well. Once a little education occurs, it's all amazingly painless. --
Andrew
_______________________________________________ newbies mailing list [EMAIL PROTECTED] http://phantom.byu.edu/cgi-bin/mailman/listinfo/newbies
