RE: Samba install problems

[Harold Hunt <Harold at compasstechnologies dot com>]

DJ,

When running setup.exe from my Samba share, U:, I get the following log
results:
mbox fatal: Can't open latest/ash/ash-20000823.tar.gz.tmp for writing: No
such file or directory

/var/log/samba/log.bones contains the following error message:
[2000/09/11 13:57:51, 0] smbd/open.c:open_directory(1188)
  open_directory: unable to create disks/cygdown/latest/ash. Error was No
such
  file or directory

When running the same setup.exe on C: I get no such errors.

The following program fails as well, giving the same message in the Samba
log file:
int main(int argc, char* argv[])
{
	int						iResult = 0 ;
	DWORD					dwError = 0 ;

	iResult = CreateDirectory( "U:\\disks\\cygdown\\latest\\ash\\", NULL
) ;
	
	if (!iResult) {
		dwError = GetLastError() ;
		cout << "CreateDirectory failed: " << dwError << endl ;
	} else {
		cout << "CreateDirectory succeeded" << endl ;
	}

	return 0;
}

However, CreateDirectory("U:\\disks\\cygdown\\latest\\", NULL ) works, note,
u:\disks\cygdown exists at time of call, but u:\disks\cygdown\latest does
not exist; it seems to me that Samba fails on CreateDirectory calls that
attempt to create nested non-existent directories.  I'm guessing that this
has to have showed up as a bug report for Samba, as CreateDirectory is
primarily used for creating several directories at once, so this has
probably been fixed after Samba 2.0.6, but I have yet to check for such a
bug report.

Harold L Hunt II
Phone: 800-850-1616 ext 108
Email: harold@compasstechnologies.com

-----Original Message-----
From: DJ Delorie [mailto:dj@delorie.com]
Sent: Monday, September 11, 2000 1:35 PM
To: harold@compasstechnologies.com
Subject: http://63.106.166.5/KB/HowTo/CygXFreeInstall.htm


  "I have run into problems using the setup program when I try to save
   the downloaded packages to a Samba share, such as, ?file
   ash-20000323.tar.gz.tmp could not be opened?; therefore, I
   recommend that you save the downloaded packages to a native Windows
   share, or a local drive, to which you have full permissions."

Sorry, this is wrong.  Setup works just fine with Samba partitions.
If you are having problems with file permissions, you need to fix it
or choose another directory.  Note that you can have permission
problems on a *local* directory as well, it has nothing to do with
samba (except that samba, like any other file server, allows you to
limit access to directories you choose).  The solution is to choose a
directory that you can write to, either elsewhere on the samba share,
or on a different share.

Please re-word this paragraph in your document to more accurately
describe the nature of the problem and the solution.

Thanks!
DJ