I made some tests here and want to share my results with you.
My configuration is:
distro: Conectiva 7.0
Kernel: 2.4.18 (compiled)
Samba: 2.2.7a (compiled)
dosemu 1.1.4.9 (compiled)
Used dbu and a simple clipper program with following source:
>USE DBFFILE SHARED
>IF !RLOCK()
> ALERT('LOCKING CODE WORKED')
>ENDIF
>INKEY(0)
Test 1: Two dosemu sessions in same linux box accessing local filesystem
DBU
When I open a file in a dosemu session, the second one makes dbu show a
red warning dialog saying Open error (Dos error 5), and show trhee options:
Quit, Retry and Default. If I choose Default, dbu gives me expected result:
does not abort, show only name of file and display this message: No active
field list in current select area.
SIMPLE PROGRAM
Worked fine. No error messages and second dosemu session saw lock made by
first one.
Test 2: dosemu accessing local filesystem and Windows workstation
DBU
dosemu and Windows open file without problem and without any error. That is
wrong because dbu opens file exclusive and once opened it could not open same
file again.
SIMPLE PROGRAM
Worked fine. Both windows and Linux could see each other lock.
Test 3: Two dosemu session, one accessing local filesystem and other smbfs
DBU
Worked same way as Test 2
SIMPLE PROGRAM
Failed. Both did not see lock made by the other and could lock again.
Test 4: Two dosemu sessions accessing both smbfs
DBU
Worked same way as Test 2
SIMPLE PROGRAM
Worked fine. Both dosemu session could see locks made by other.
Test 5: dosemu acessing smfs and Windows
DBU
Same way as Test 2. But something really wrong happened here. I quit dbu from
dosemu and Windows still sees file as locked.
SIMPLE PROGRAM
Failed. Windows and dosemu did not see lock made by the other and could lock
again.
Hope my results can help you. I could not test nfs, because my other Linux
boxes are using kernel 2.2 and for now I can not upgrade them.
[]s
Anderson Pereira Ataides
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
