tmpnam is said to create a temporary file in the current directory. If
just checked the code. It could be, that if you can't create a file in
the current directory, then this error condition is not properly
handled.
From a quick glance through the code it could also be that you will see
the behavoir, that you describe.
In the current directory, or in %temp% (or whatever Windows uses for
the standard user temporary directory)? There's no reason to assume
you can write to the directory containing the VSS file, but you should
always have rights to create files in %temp%.
My Linux man page for tmpnam says it creates the name in the directory
specified by P_tmpdir, defined in stdio.h. For Linux this is /tmp.
Strange, the MSDN tells a different story:
Each of these functions returns the name of a file that does not
currently exist. *tmpnam* returns a name unique in the current working
directory ...
see http://msdn2.microsoft.com/en-us/library/hs3e7355.aspx
But you are right, I remember that I had a few temporary files in my
root directory. But I have never checked the root cause for this.
Dirk
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
