[Samba] AutoCAD temp file error

[Rich Forman]

I continue to have this problem w/ LDD and it occurred even before I
switched from an NT server to Samba.  I'm fairly certain it's an Autodesk
problem.

-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of Brock Nanson
Sent: Friday, November 01, 2002 8:31 PM
To: Jay Ts
Cc: samba at lists.samba.org
Subject: Re: [Samba] AutoCAD temp file error


Hi Jay,

> 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.

Perhaps.  But the config hasn't been touched in 2 years and the WinXX
workstations have never had the problem.

> > 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 filename looks like this: $abc$de.dwg

The letters aren't right (I can't recall them exactly right now), but the
file does start with a '$' and has a second on part way through as shown.

I think the key to this is hidden in the way I can 'seed' the directory with
this file once and have the command work until a new drawing is opened after
doing so.  Note that the file is deleted as a matter of course and that the
file is not there the second, third,... time the command is used and it will
work.  But I need the file there the first time!!

> > 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.

Yeah, can't do this as I do use a Windows based backup utility.  Funny that
this file is the only one saved with the execute bit toggled.  The other
files AutoCAD creates don't have the execute bit set.

> > 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!

That's actually four words, but I do agree ;-)

> > 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? :)

I did think of it but as I'm writing these postings away from the system
couldn't remember the exact file name.  I'm not very familiar with win2k but
found it strange that it differentiates between 'Nobody' and 'nobody'.  That
has me a little worried, but as I can use the work around described above, I
don't think the 'N' vs. 'n' is a problem.  I do think it is a win2k issue,
but it is odd that the problem can't be recreated when using a local drive.

Any other ideas??

Thanks,

Brock