Using Samba 1:3.0.28a-3 from Debian sid with a Windows XP SP3 client.
I'm have an odd problem using the third-party copy utility teracopy.
Although copying from a samba share works fine with the default Windows
Explorer client, if I use teracopy, the operation frequently gets stuck,
and I see
Hi All,
Samba with default configuration is used to access ClearCase from PC. It
works fine for all users.
But JBuilder user session hangs for ClearCase data, after some time.
JBuilder hangs hang and it stops their work.
The log file tells about oplock and sample error is as below :
request_o
-- Forwarded message --
Date: Tue, 29 Jul 2003 19:40:48 -0400 (EDT)
From: Rashkae <[EMAIL PROTECTED]>
To: Marco De Vitis <[EMAIL PROTECTED]>
Subject: Re: [Samba] oplock problem on NTUSER.DAT
Hi Marco
Try to veto oplocks for that file.
In the global section of your s
Hi,
I'm on a network with a Samba 2.2.8a fileserver + PDC (Mandrake Linux
9.0) and various Win2000 Pro clients.
Very often, when I log off from one client and log on a different one
soon after, I get an error message telling me that the remote profile
cannot be loaded, and the local one will be use
<[EMAIL PROTECTED]>
To: "Boogerman" <[EMAIL PROTECTED]>
Cc: "John H Terpstra" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, May 07, 2003 10:21 AM
Subject: Re: [Samba] Oplock problem
> I've never been comfortable with the concept of oplocks m
t;[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, May 08, 2003 10:37 AM
Subject: Re: [Samba] Oplock problem
> In this case, I would disable oplocks. My earlier post was only to point
> out that with Samba, you can disable oplocks selectively on files that
> might cause
On Tue, 2003-03-25 at 01:11, Alok Bhatt wrote:
> We are thinking of shifting to latest version of samba, but will that help
> or will we have to make further changes. Please help if anyone has gone
> through the problem.
>
yes that will help - there were oplock bugs fixed recently.
your other ch
Hi All,
I am using Samba Version 2.2.3a on Red Hat Linux 2.4.18 and am having
trouble in the settings. Quite a lot of clients have been saying that their
PCs hang, whenever they access our server which acts as file and print
server. The logs show messages of oplock break A portion of log file is :
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Joel Hammer
> > Sent: Friday, September 27, 2002 9:05 PM
> > To: Sean Noonan; [EMAIL PROTECTED]
> > Subject: Re: [Samba] oplock problem
Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Joel Hammer
> Sent: Friday, September 27, 2002 9:05 PM
> To: Sean Noonan; [EMAIL PROTECTED]
> Subject: Re: [Samba] oplock problem - how to fix?
>
>
> How can you get an oplock error
EMAIL PROTECTED]]On
> > Behalf Of Joel Hammer
> > Sent: Friday, September 27, 2002 7:00 PM
> > To: Sean Noonan; [EMAIL PROTECTED]
> > Subject: Re: [Samba] oplock problem - how to fix?
> >
> >
> > man smb.conf
> > / oplocks
> >
>
(yes, I restarted
daemons after each change).
Any more ideas?
-- Sean
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Joel Hammer
> Sent: Friday, September 27, 2002 7:00 PM
> To: Sean Noonan; [EMAIL PROTECTED]
> Subject:
man smb.conf
/ oplocks
Essentially, turn off oplocks.
Joel
On Fri, Sep 27, 2002 at 06:33:29PM -0700, Sean Noonan wrote:
> Hi everyone,
>
> Trying to copy a 3.5MB file from a Windows 2000 workstation to a FreeBSD
> 4.6.2 server running samba-2.2.6.p2. The 3.5MB file is an MS Access file
> c
Hi everyone,
Trying to copy a 3.5MB file from a Windows 2000 workstation to a FreeBSD
4.6.2 server running samba-2.2.6.p2. The 3.5MB file is an MS Access file
called MoldFE.mdb. After a few seconds of copying the file, a message box
pops up on the W2K workstation that states "Cannot copy MoldFE
On Fri, 31 May 2002, Dennis Lattka wrote:
> We are continually getting the following messages in the logfile, which
> consistently results in corrupted files. Mainly MSOffice 2000 files as
> well as FileMaker Pro DB corruption.
See the recent thread on samba-technical about oplocks and Win9x cli
We are continually getting the following messages in the logfile, which
consistently results in corrupted files. Mainly MSOffice 2000 files as well as
FileMaker Pro DB corruption.
error message:
[2002/05/30 14:30:10, 0] smbd/oplock.c:oplock_break(761)
oplock_break: receive_smb timed out after 3
16 matches
Mail list logo
