From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Charlton Subject: Re: Running Clipper programs in network environment Date: Sat, 4 Oct 2003 18:14:34 -0400 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <200310041814.34221.j.d.charlton@ieee.org> References: <3F7E9888.6000805@EUnet.yu> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <3F7E9888.6000805@EUnet.yu> Content-Disposition: inline List-Id: Content-Type: text/plain; charset="iso-8859-1" To: =?iso-8859-1?q?G=E1bor=20Dukai?= , linux-msdos@vger.kernel.org On Saturday 04 October 2003 05:53, G=E1bor Dukai wrote: > Hello! > I have a small office network (4-6 clients), where we have to use a > Clipper-based program for bookeeping. First, we used an old NetWare a= s a > server, then I replaced it with linux+Samba. It worked for a month bu= t > we had some corruption in the databases. Browsing the Net for a new > solution I have found an interesting one which was discussed on this > list a year ago or so. Now the server runs multiple instances of dose= mu > and the clients access them through X. Now we have no corruption but = it > gets really slow around 4 clients connected (with 1-2 clients dosemu > runs well). Is it possible to speed it up somehow (new hardware?) or = I > have found a theorically wrong solution again? > > > Thank you for your help, > G=E1bor Dukai The corruption of the databases you had with linux/samba is probably du= e to=20 file sharing/locking problems. We have tested file locking/sharing wit= h=20 dosemu 1.1.5.0 and freedos kernel.sys 2032 (no share.exe needed for dos= emu)=20 using nfs mounted network drives with linux/dosemu clients. File=20 sharing/locking works well with this configuration We are not using cl= ipper,=20 but if clipper supports multiuser file locking/sharing it should work. = We=20 have not tested locking with samba mounted network drives. --John - To unsubscribe from this list: send the line "unsubscribe linux-msdos" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html