search for: getatrs

...l versions of samba 1.9.18 from p3 which we use as standard through to p10 If I try to close down vc++ after making some modifications to the workspace (adding a file to a project). vc ++ tries to update its on-disk config. and fails. The following are the operations I see in the log (minus a few getatrs). In the following: vcb is ~vcb.tmp and mf.opt is the file mf.opt. open vc68 new file readonly fnum 64 close 64 open vc69 new file readonly fnum 65 close 65 unlink vc68 find mf.opt open vc68 new file writeable fnum 66 write 66 ......... write 66 ? open vc68 readonly break our own oplock fnum bre...

Could anyone tell me what I may be doing wrong here? I'm using samba-1.9.18p8 on a Linux 2.0.32 box, RedHat 5.0 install. I can descend into this share from a WinNT box just fine, but get the following error messages from a Win95 box. Thank you all in advance, -Jon Charette --------- Start log at debug level 4 ---------------------- 1998/07/08 13:20:22 Transaction 52 of length 47 switch

Sorry that I will ask a kind of a vague question, but I don't really know how to proceed at the moment: Some of our Samba (1.9.18p10) users experience the following problem: they map a drive to a Samba share (pointing into AFS, if that matters) and see all files/dirs correctly after the password dialog. 'Some time' later (for one user usually about one hour) they try to use the drive

A PC running Windows 95 has a share mounted from a Samba 2.0.7 server running under Mac OS X Server. An attempt is being made to copy a file on the PC called suse.iso to a subdirectory of the share (faberlab) on the Samba server. The PC hangs a bit and eventually complains that it can't create the file. Here is the debug log starting from the moment the copy has begun... [2000/06/02

Hi! This is a really weird problem, I hope, someone can help me out there. First of all, I put my smb.conf on the web, you can find it here[0]. The Sambaserver (ESS-LINUX) is just an ordinary workstation (in the terms of SMB) and uses the PDC (ESS_SERVER) for authentication (see "password server"-directive). Nearly everything works fine. Each authenticated user gets his home-directory

Hi all, I've a BIG problem on a Unix SunOS 4.1.4 running SAMBA (samba-1.9.18p3) in order to export some file systems to WindowsNT client machines. The client are using Visual C/C++ 5.x for compiling files (source are remote, but binary are generated on local disks). The problem is that the CPU time and the IO goes... too UP (I've a load average of 8)!!! I traced the clients (with log

I'm having a problem with files locking so that every time the are opened up they are opened as Read-Only. Windows doesn't see them as readonly but Samba thinks that they are write=no and so they can't be saved or deleted. I've included a log, my smb.conf, and a getfacl of a user's home directory as well as a getfacl of the directory from /home. Any help would be

I'm trying to copy a 400 MB file from a Windows 98 host to a FreeBSD 4.5 Samba server providing access to a FAT32 filesystem. I've got "strict allocate = no", but from what I can see with debug set to 10, it is doing a ftruncate which takes about 50 seconds to complete. It appears that Windows gets impatient and generates an error (while Samba is still waiting for the