similar to: smbfs: correctly propogating locks?

Hi, First of all, apologies if I'm not posting this in the correct place. I'm successfully running Microsoft Visual Foxpro 7 under Wine, however I needed to use the native versions of shlwapi and oleaut32. There is a major problem still, however, and that is that foxpro will freeze as soon as I use the mouse to click in certain controls (the command window, a textbox, an edit box,

I'm trying to get our legacy Microfocus Cobol database interface to work on a Linux box. I'm using WINE 20021007 built from source on Mandrake 8.2 (after removing default WINE install) I've fixed several problems in my config file, and imported some dll's that were missing. I can get to the login screen, but when I try to go any farther into the program I get this:

I'm trying to run a Visual FoxPro 6 application that writes to a Samba share. It crashes with "LockFile not implemented in server" and "UnlockFile not implemented in server" messages. I've attached a more complete log file to this message. On the Samba server, there aren't any special locking restrictions: for example, oplocks are allowed. Any ideas will be

Hi, I just (~1100h CET) pulled the current wine release from CVS (as I do almost every morning ;-), compiled and now my Lotus Notes client does not complete its startup anymore (yes, I know CVS is bleeding edge...) I get lots of fixme:file:LockFile not implemented in server fixme:file:UnlockFile not implemented in server messages, the window is being created, the menu bar is being drawn and

Hi, I use software that is supposed to access hardware using the ASPI layer. But whenever I open the software I get the error: could not acces the device. Precisely the same message one gets, when the aspi layer isn't installed in Windows. Looking at what I get with "wine -debugmsg +file" I don't see any wnaspi32.dll or similar loaded. Without the debug on, I get errors

We have a Windows application that uses shared archive files in local network: one computer acts as server and stores the physical archive files and all clients connect to that server with samba for directly reading and writing archive files in multiple access. For file managing the application uses the Windows API: CreateFile, CloseHandle, LockFile, UnlockFile, SetFilePointer, ReadFile,

Hi Urban smbfs modifies some memory after free... smb_get_length: Invalid NBT packet, code=4a smb_add_request: request [d828617c, mid=1802201963] timed out! Slab corruption: start=d828617c, expend=d8286287, problemat=d8286184 Last user: [<ec992e35>](smb_free_request+0x45/0x4c [smbfs]) Data: ********6A

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:16.smbfs Security Advisory The FreeBSD Project Topic: smbfs chroot escape Category: core Module: smbfs Announced: 2006-05-31 Credits:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:16.smbfs Security Advisory The FreeBSD Project Topic: smbfs chroot escape Category: core Module: smbfs Announced: 2006-05-31 Credits:

I have samba 3.0.10 running on a Debian server. I have other Debian machines which use smbfs (also 3.0.10) to mount the share. Every now and again, the mount will lock and an ls inside it produces an i/o error. If i try to umount the share, it gives me a share busy error. Now, there is no real i/o error on the server. I have ten client machines total which mount shares from the server, and

Vlad. I still got the same problem - 'ls | wc -l' returned incorretc numbers. I installed the following patches with the sequence vs. the kerner 2.4.18: 1. 00-smbfs-2.4.18-codepage.patch.gz 2. 01-smbfs-2.4.18-lfs.patch.gz 3. 02-smbfs-2.4.18-unicode.patch.gz 4. smbfs-2.4.19-pre9-readdir.patch After installed patches, I ran 'make modules' and so on. Any more

The patch below makes some needlessly global functions static. diffstat output: fs/smbfs/inode.c | 2 +- fs/smbfs/proc.c | 6 +++--- fs/smbfs/proto.h | 5 ----- fs/smbfs/request.c | 6 ++++-- 4 files changed, 8 insertions(+), 11 deletions(-) Signed-off-by: Adrian Bunk <bunk@stusta.de> --- linux-2.6.10-mm1-full/fs/smbfs/proto.h.old 2005-01-04 00:57:42.000000000 +0100

I know smbfs is not samba, but perhaps somebody here has seen this error before. Basically, I can't use smbfs: [root@pandora samba]# mount //buildmaster/andreas -o username=andreas -t smbfs /mnt/smbfs added interface ip=10.0.17.30 bcast=10.0.23.255 nmask=255.255.248.0 error connecting to 10.0.16.6:445 (Connection refused) Password: [root@pandora samba]# ls -la /mnt/smbfs ls: /mnt/smbfs:

I periodically see smbfs questions get asked on this list, and they usually get one of two responses: 1. smbfs is a kernel module; this list is not the appropriate place to be asking smbfs questions. 2. You should be using cifs instead. (Please let me know if either if these is incorrect.) I was surprised to see, however, that the smbmount / mount.smbfs manpage makes no mention of cifs as being

I'm using Samba & smbfs to make directories on a Linux file server available across a switched Gigabit network. Unfortunately, when mounting the shares to another Linux system with smbfs, the performance is terrible. To test the setup, I created both a 100mb and 650mb file and transferred them with ftp, smbclient, and smbfs (mounted share). I also used iperf to send each file, just out of

My apologies in advance if this is considered off-topic, but I'm trying to install a Linux devel kernel (2.1.53) and Linus' CHANGES doc tells me I need smbfs 2.1.0 to compile the SAMBA stuff. Installed SAMBA: 1.9.18p5-50.6 Installed smbfs: 2.0.1-2 Question is: I can't find any smbfs code later than 2.0.1-2 on ftp.redhat.com. I've looked at the SAMBA pages and used the search

First I will apologize for posting my patch here if this is not the correct place to post a patch. I know that smbfs is being removed, but we still use it and need it to work. We have a patch to contribute back to the smbfs in the 2.6 kernel. I have noticed multiply posts on this issue and we have basically patch the smbiod.c to fix the reconnect bug in 2.6 Something we did for our patch is

Hello everyone I have recently reported problems reading a certain directory from an NT server on this list (and speculated in causes). I have a few workarounds and now I'm looking for some feedback on what the proper fix is and for people to test if my patch works for them. Please test smbfs with and without the patch on the directory in this zipfile (all files are empty):

Can someone share the smbfs-2.4.19-pre9-readdir.patch. -----Original Message----- From: David.Lee@bisus.com [mailto:David.Lee@bisus.com] Sent: Tuesday, June 25, 2002 4:21 PM To: vlads@sympatico.ca; urban@teststation.com Cc: samba@lists.samba.org; David.Lee@bisus.com Subject: [Samba] RE: [PATCH] smbfs readdir fix (CFT: NetApp, OS/2) Vlad. I still got the same problem - 'ls | wc -l'

Hi! Here's a patch that allows Linux smbfs to list large directories (i.e. > 100 items) when talking to an OS/2 server. There is a misunderstanding about the flags sent in the FINDFIRST request which causes the OS/2 server to indicate an EOS (end of search) in the FINDFIRST response, even when there are more items to be listed. The result is that smbfs will display only the first ~120