On Tue, 11 Feb 2003, Anderson Pereira Ataides wrote: > 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.
You could produce -D+Dd a log for this case and send to me privately. You could also try 1.1.4.13 and see if that makes a difference. > 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. here you could have to look into your Samba settings, and also see what lsof says about the file when it's opened by the Windows client. > 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. it would be worth to make a log for this case too so they can be compared. Note however, that if your two DOSEMU sessions are on the same host (what I suspect from your writing) they might be able to see each others locks because these locks go through the Linux kernel VFS (virtual file system) instead of travelling through smbfs. What I suspect here is that some locks are kept in the VFS whereas others are not and that's what makes the difference for DBU. Bart - 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
