I rather doubt this is a samba problem, but perhaps someone can offer a hint to solve the issue... Running AutoDesk Land Development Desktop (AutoCAD with add-ons essentially). The project data files are on the Samba server. A dozen WinXX workstations work flawlessly with this configuration (other than typical windows issues). A win2k workstation was recently added to the mix and it works too, except for a set of functions that generate temporary files. Essentially what happens is this: - the command blocks out a selected portion of the drawing to a temporary file and puts the file in the same directory as the drawing (i.e. on the server). - the command then changes a mode in AutoCAD and attempts to insert this file into the drawing. - the temporary file is then deleted. The win2k box fails, saying the file could not be found on the path (and dumps a listing of the paths checked). The path exists in the list, and the file has been written to the directory! When the user responds to the error and the command completes, the file is successfully deleted from the server. So, it is doing everything except finding and inserting the file (which is there!). A work around is to copy this file to a new name then rename to the temporary name used by the function. The next time the command is invoked, the routine behaves properly, deleting the file when complete. The really strange thing is that the command will work after this until a new drawing is loaded for editing!! That baffles me! The temp file on the server is being saved with rwxrw-rw- attributes, although all the other files are rw-rw-rw-. All files in the directory are set to user and group 'nobody'. Doing a properties check on the file from Win2k shows the file to be owned by 'Nobody' with rwx priviledges, but user 'nobody' is also listed with read only rights. I don't think that can be related as the command can be made to function as described above. I had wondered briefly if the speed with which the file is saved, then requested could be a problem. It probably hasn't been written to the drive by that time - it's on a software RAID5 - but that shouldn't matter... Any guesses? Or even a confirmation that the problem is with Win2k and NOT the samba box? I should add that moving the project folder to the local drive on the win2k box allows the command to function properly. Maybe it is a samba issue? Thanks, -- Brock Nanson Kamloops BC Canada
Brock Nanson wrote:> I rather doubt this is a samba problem, but perhaps someone can offer a > hint to solve the issue...It's very unlikely to be a Samba bug, but may very well be a Samba misconfiguration.> The win2k box fails, saying the file could not be found on the path (and > dumps a listing of the paths checked). The path exists in the list, and > the file has been written to the directory! When the user responds to the > error and the command completes, the file is successfully deleted from the > server. So, it is doing everything except finding and inserting the file > (which is there!).Exactly what is the name of the file, and are you using any foreign languages in file names? If you are using anything other than English, be aware that support for internationalization in Samba 2.2 is a little complicated to set up, and may be the source of your problem. Even if your file names are in the American/English character set, there are differences between how Unix and Windows handle filenames. A common source of trouble is case sensitivity in filenames. There are parameters that can be set in the Samba configuration file (smb.conf) to help deal with this.> The temp file on the server is being saved with rwxrw-rw- attributes, > although all the other files are rw-rw-rw-.That is because Samba's default is 'map archive = yes'. When the archive bit is set on a file from MS-DOS/Windows, Samba will keep track of it using the owner's execute bit. It will look like an executable file to a Unix user. If you don't like this, then set map archive = no in smb.conf. After doing this, MS-DOS backup software may not work right, because it won't see any archive attributes set for files to incrementally back up.> I had wondered briefly if the speed with which the file is saved, then > requested could be a problem.In a word: no. In three words: I highly doubt it!> Any guesses? Or even a confirmation that the problem is with Win2k and > NOT the samba box?I certainly wouldn't guarantee it's not a Windows bug. ;-) If you haven't fixed the problem by now, try providing a little more information, specifically, the _exact_ name of a temporary file that is problematic -- didn't you think of including that in your question? :) Jay Ts