I get this errors too in Samba on Linux kernel 2.4.16 with/without acl of bestbits.
The problem is whith clients accessing from wondows 2000 workstation using a Visual Basic 16 bits application to Foxpro 2.5 files. Any Idea? Pablo Ladner, Eric (Eric.Ladner) wrote: > Got anohter one > > > > [2002/04/26 10:49:36, 0] smbd/oplock.c:oplock_break(758) > oplock_break: receive_smb error (Error 0) > oplock_break failed for file budget/2003Budget/RefinerySchedule.pdf > (dev = 40000005, inode = 60589, file_id = 2168). > [2002/04/26 10:49:36, 0] smbd/oplock.c:oplock_break(843) > oplock_break: client failure in break - shutting down this smbd. > > They seem to always come in pairs and result in an error on the client > side. The file is not saved. > > > > Should I turn off oplocks altogether? > > -----Original Message----- > *From:* Ladner, Eric (Eric.Ladner) > [mailto:[EMAIL PROTECTED]] > *Sent:* Thursday, April 25, 2002 11:39 AM > *To:* '[EMAIL PROTECTED]' > *Subject:* [Samba] Oplock breaks. > > (HP-UX 11.0 - smbd version 2.2.3a) > > > > Any idea what causes this: > > > > [2002/04/25 07:55:21, 0] smbd/oplock.c:oplock_break(758) > oplock_break: receive_smb error (Error 0) > oplock_break failed for file nalco/TMPfpd8cv4jv7.shtml (dev = > 40000005, inode = 60549, file_id = 2501). > [2002/04/25 07:55:21, 0] smbd/oplock.c:oplock_break(843) > oplock_break: client failure in break - shutting down this smbd. > > At the same time, the user got one of those "The local device name > is already in use" messages. > > > > We've started seeing a lot of these in the last few weeks or so. > > > > Thanks, > > > > Eric Ladner > > Chevron Products Co. > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
