similar to: NT & Win98 slow copies

tl@fairplay.no wrote: > Hmm, I missed the original post, but this sounds like it could be the bug > I reported 15 days ago to samba-bugs (PR#8316) and still haven't got any > responses to. > Sorry, I'm still integrating incoming patches. > If it's the same bug it's mainly the write performance that's bad, and in > reality the performance is worse than

When the world was young, Adam Snodgrass carved some runes like this: > Date: Mon, 10 Aug 1998 19:06:07 -0400 > Subject: Failure to execute programs from a mapped drive letter on a samba > I have a strange situation. I have a Linux machine running samba > 1.9.18p8, serving a mix of NT Workstation 4.0 and Windows 95 clients. In > general, things have worked flawlessly, with one

> Further to my previous post, I have made an interesting discovery. This > particular slowdown only occurs from clients that are running > Windows 98. The Windows98 explorer (and possibly other programs) incorrectly set the "sync" bit in write requests to network shares. This causes an enormous slowdown as Samba (quite correctly) does a fsync() on the file after each write.

PLEASE, PLEASE DELETE ME OFF THE MAILING LIST. I HAVE SENT SEVERAL MESSAGES REGARDING THIS!!! THANK YOU -----Original Message----- From: samba@samba.anu.edu.au [SMTP:samba@samba.anu.edu.au] Sent: Thursday, August 13, 1998 1:09 PM To: Multiple recipients of list Subject: SAMBA digest 1778 SAMBA Digest 1778 For information on unsubscribing see http://samba.anu.edu.au/listproc

People, Please could someone in the know help me out with the shared memory configuration (/etc/system?) required on Solaris 2.5 and above to support samba with about 1000 open files per process. Since 1.9.18p3 I have been getting errors like: Apr 2 12:15:39 skyhawk smbd[27493]: Can't create or use IPC area And now with 1.9.18p4 I get the same, plus: Apr 2 12:15:39 skyhawk smbd[27493]:

Hello list, We discovered that it was impossible to compile Samba 1.9.16p10 on SCO Openserver 3.2.2 (native compiler). Here's a small patch that fixes this problem: ----cut here---- *** includes.h.orig Sun Feb 23 04:26:40 1997 --- includes.h Mon Jun 30 16:18:27 1997 *************** *** 668,692 **** #include <prot.h> #define crypt bigcrypt #endif - #ifndef EVEREST -

> Date: Wed, 5 Aug 1998 11:20:57 -0400 (EDT) > From: Dan Roscigno <ddr@phys.ufl.edu> > To: Multiple recipients of list <samba@samba.anu.edu.au> > Subject: Re: SAMBA digest 1769 > Message-ID: > <Pine.SOL.3.96.980805111839.9665I-100000@neptune.phys.ufl.edu> > > > Hay, > > I have a big problem with the stop e start smbd. > > I start the samba

We've begun a network migration project to migrate from an old and pretty broken NT 4.0 domain (Lots of settings are just wrong and we wanted to rename the domain at the same time) to a Windows 2003 based AD domain. One of the issues we need to resolve is that all our users' My Documents are mapped to their home share on a Samba server I've been pondering how I can easily get both

Hi all: I am experiencing a problem where WinNT and Samba are dropping connections during file transfers. I have the following smb.conf settings: keep alive = 30 dead time = 1440 socket options = IPTOS_THROUGHPUT SO_KEEPALIVE (although I tried IPTOS_NODELAY with no apparent benefit). The client is copying a large number of files up to the server, then there is a pause at a random file,

We are having a problem with Microsoft visual C++ compiling source code maintained on a samba server. Occasionaly the compiler reports that it cant open the file vc50.pch. The samba server is running on a freebsd box. Taking a look at the log files it looks like when the operation fails the server is processing the command open (vc50.pch for exclusive use write setattrE write open (vc50.pch

We are running Redhat 9, 2.4.20-30.9 kernel, Samba 3.0.0 and Winbind 3.0.0. Security is set to "Domain" and we are trying to set up shares which will be available to valid NT 4.0 users and groups. Winbind appears to be working, and you can use the commands "getent group" and "getend passwd" to see that it is communicating with the NT domain for user and group

Hi quite strange assumtion, but I have the feeling, that samba makes my NT-CLient crash (blue screen). I haven't found anything in the archives about such troubles. It dosn't matter whether sp3 is installed on the NT machine, nor does a specific samba version makes this behavior vanish, it's just that my samba server wasn't available for a 3 months period in which the NT

Greetings ! Using Samba-1.9.16p11 on RedHat4.2 Linux as tape server, and backing up SCO3.2v4.2 running Samba-1.9.16p11, when I....... smbclient \\\\scobox\\share -TcX /dev/st0 dev cdrom floppy proc After a sustained successful partial backup, I get............. Expected SMBtrans2 response, got command 0x00 Segmentation fault, core dumped This seems to occur at about the same point in

I just thought that I would put this out there and see if anyone else sees this problem with Samba 1.9.18p4 (under Solaris 2.6). It appears that after some reboots of Solaris, Samba printing is partly dead. What I see in the logs are below, and what happens is that the file to be printed is spooled to /var/spool/samba, like always, but when the lpr command is issued it croaks. I've been

I can?t copy some files from server to directory /adawork/softtek om AIX box I?m using AIX 5.3 with samba 2.2.7-4 Here?s mys logs from samba server _________________________________________ file log.windows-server seek_file: (FAT_ATRASO_TRANS_5_3_1_in.txt) sys_lseek failed. Error was Invalid argument [2009/08/27 13:30:59, 3] smbd/error.c:error_packet(94) error string = Invalid argument

Here's the scoop, Well Jeremy and I found the bug last night. Unfortunately it will not be fixed soon. The problem is a bug in our client side code wrt oversized PDUs. When the needed size > MAX_PDU_SIZE in a parsing struct, we need to fragment the PDU and use SMBwrite instead of a single SMBtrans. Fortunately, this has not gotten us into big trouble yet. Jeremy knows how to fix it,

I posted a while back about getting very slow writes. People suggested modifying (increasing) SO_SNDBUF and SO_RCVBUF and this actually helps enormously. However, there is obviously something still not right. Writes are still about 1/2 the speed of reads. This only seems to affect Win95 clients (NT machines are fine). Doing a write of a 20mb file to the server generates the following message:

When the world was young, Klaus Kappel carved some runes like this: > Date: Thu, 30 Jul 1998 12:05:08 +0200 (CEST) > From: Klaus Kappel <kkappel@sha2000.de> > To: samba@samba.anu.edu.au > Subject: Locking with M$-Access 97 > This is a REAL problem on the way to world domination ;-) > since we moved a MS-Access MDB (16 Meg) to samba, > it ist killing queries more

The patch below removes an outdated samba ChangeLog file. diffstat output: fs/smbfs/ChangeLog | 160 --------------------------------------------- 1 files changed, 160 deletions(-) Signed-off-by: Adrian Bunk <bunk@stusta.de> --- linux-2.6.10-rc3-mm1-full/fs/smbfs/ChangeLog 2004-10-18 23:54:55.000000000 +0200 +++ /dev/null 2004-11-25 03:16:25.000000000 +0100 @@ -1,160 +0,0 @@

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