Bug 4048 - Problem of Corruption of data in DataFlex DataBase
Problem of Corruption of data in DataFlex DataBase
Product: Samba 3.0
Classification: Unclassified
Component: smbclient
Other Windows XP
: P3 critical
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2006-08-24 13:59 UTC by Guto
Modified: 2007-01-18 08:10 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Guto 2006-08-24 13:59:17 UTC
Linux Fedora4.0 2.6.11-1.1369_FC4 with samba  3.0.14a-2
Windows: XP, 2000,98,95
The DataFlex Database is ISAM (direct by record), is different from database 
related Client/Server like the Pervasive SQL, DB2, SQL Server, Oracle, etc.
1.2-Dataflex for Linux:
It´s software installed in the linux server where clients access with the telnet or SSH.
1.3-Visual Dataflex:
Application developped in environment Windows.

Our system is developped in Dataflex for linux (character in procedural) an another part 
of it developped in environment Windows, accessing the same base in the server linux.
The locks of files are working separately. Example: when i try to record something in my
application Windows XP, in an open file by emulator Telnet, this file is damaged.

Let´s use the following configuration in the Samba with the version 2.x

[name of compartilhamento]
locking = yes
oplocks = yes
veto oplock files = /*.dat/*.DAT/*.k*/*.K*/*.cfg/*.CFG/*.vld/*.VLD

In register of Windows XP sp2:
Value = 1

Value = 0

This worked correctly.

With the new installations of Linux with samba 3.x it stopped working.

We would like to know if it exists some other configuration, to the version 3.x which 
has the same behavior of the version 2.x in order our systems can work in perfect harmony.

When I make downgrade for Samba 2.x , this problems finished.

Thank you.

Abaco Informática
+55 11 3333-3234
Brasil - São Paulo - SP
Comment 1 Gerald (Jerry) Carter 2007-01-18 08:10:03 UTC
Please retest with 3.0.23d and reopen ifg the bug still persists.