[Samba] problem with samba and a dos application
Hello all, I am trying to export a share to several Windows clients, that start some application in a dos box. The application itself is located on the share. The first client can start it, the second cannot. It looks like a locking problem, but experiments with "locking = no" showed no effect. The application in question is OpenAccessIII (SPI), just in case somebody knows it. Any hints are welcome. -- Regards, Stephan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] problem with samba and a dos application
On Tue, 2002-11-26 at 09:40, Stephan von Krawczynski wrote: > I am trying to export a share to several Windows clients, that start some > application in a dos box. The application itself is located on the share. The > first client can start it, the second cannot. I have a client whose major application is a DOS based product and it works fine running just like this. Is the product designed to be network shared like this? Does it work correctly when the server is a Windows box? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] problem with samba and a dos application
On 26 Nov 2002 10:06:49 -0500 Chris Smith <[EMAIL PROTECTED]> wrote: > On Tue, 2002-11-26 at 09:40, Stephan von Krawczynski wrote: > > > I am trying to export a share to several Windows clients, that start some > > application in a dos box. The application itself is located on the share. > > The first client can start it, the second cannot. > > I have a client whose major application is a DOS based product and it > works fine running just like this. Would you mind to allow me a look in the smb.conf (in private email)? Maybe there is some difference ... > Is the product designed to be network shared like this? The funny part about it is: I am trying to migrate a working setup where the "server" is MARS (nwe) (netware server simulation under linux) to samba, everything else identical. The same dos application is working fine with nwe "shares" and can be started several times without any troubles. > Does it work > correctly when the server is a Windows box? I can't tell, I have no windows server at hand currently. What can I do to find out exactly what filesystem actions are causing the troubles? -- Regards, Stephan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] problem with samba and a dos application
On Tue, 2002-11-26 at 10:17, Stephan von Krawczynski wrote: > Would you mind to allow me a look in the smb.conf (in private email)? Maybe > there is some difference ... No problem but it might be better shared here as there are many who know more than I. In my clients smb.conf we use these options for the DOS share: force create mode = 0777 force group = groupname valid users = @groupname dos filetimes = yes level2 oplocks = no oplocks = no It works with oplocks (both) on as well but they do get a bunch of oplock's breaks logged. I turned them off and they see no performance difference so I left them off. The particular product uses the btrieve engine. > > Is the product designed to be network shared like this? > > The funny part about it is: I am trying to migrate a working setup where the > "server" is MARS (nwe) (netware server simulation under linux) to samba, > everything else identical. The same dos application is working fine with nwe > "shares" and can be started several times without any troubles. Netware was particularly good at serving up DOS applications. Better than any version of Windows. > > Does it work > > correctly when the server is a Windows box? > > I can't tell, I have no windows server at hand currently. You can use any Windows box, it doesn't need to be a server, for testing. Just copy the files to a folder, share it and see if the other clients can use it simultaneously. > What can I do to find out exactly what filesystem actions are causing the > troubles? Might check the logs. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
